Skip to content

Enable fail-fast for ExtendedTestSet by adding compatibility with FallbackTestSet. - #19

Open
ktchu wants to merge 7 commits into
ssfrr:masterfrom
ktchu:kc-fast-fail
Open

Enable fail-fast for ExtendedTestSet by adding compatibility with FallbackTestSet.#19
ktchu wants to merge 7 commits into
ssfrr:masterfrom
ktchu:kc-fast-fail

Conversation

@ktchu

@ktchu ktchu commented Jul 17, 2021

Copy link
Copy Markdown

The current implementation does not support fail-fast because FallbackTestSet does not possess the same fields as DefaultTestSet. This PR adds support for fail-fast by adding compatibility with FallbackTestSet. Compatibility with FallbackTestSet is achieved by specializing the type for the original Test.record() method to ExtendedTestSet{DefaultTestSet} and adding a record(ts::ExtendedTestSet{T}, res::Fail) method that calls the record method for T.

One of the issues that arises when using FallbackTestSet is the generation of redundant error messages when test sets are nested. In this PR, this issues is addressed by suppressing output messages originating from errors generated when a test set detects that an enclosed test or test set has failed (via the introduction of a ExtendedTestSetException to distinguish between the original test failure/error and subsequent test errors).

Unit tests have been added to verify the expected fail-fast behavior.

@ktchu ktchu changed the title Enable failfast for ExtendedTestSet by adding compatibility with FallbackTestSet. Enable fail-fast for ExtendedTestSet by adding compatibility with FallbackTestSet. Jul 17, 2021
ktchu added 3 commits July 19, 2021 17:59
…ltTestSet)

* Add unit test to cover cases when nested DefaultTestSets have no
  failing tests.
* This chance is made for backward compatibility with Julia 1.0
@ktchu

ktchu commented Jul 20, 2021

Copy link
Copy Markdown
Author

I have added code for backward compatibility with Julia 1.3 and Julia 1.0. Unit tests are passing, but code coverage checks are failing due to a "Error sending Email notification: Value cannot be null. Parameter name: source" error (see attached screen shot).

Screen shot of error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant