update audigent tests to fix larger test suite issue #4952
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Description of change
When #4834 was merged, an issue was introduced to the test suite where roughly 25% of the tests were silently not running.
Currently, in the PBJS project there are ~4.7k tests that run when you execute
gulp test
. When the above PR was merged that number dropped down to ~3.1k tests. The results from the commands gave no indication that tests were skipped, it passed all fine.While I haven't identified all the exact reasons, the issue here appeared to be tied to the use of the
setTimeout
s in the test spec's logic. While thesesetTimeout
appeared to work fine prior to the above commit, this 25% test issue disappeared for good when that setTimeout code was removed from the spec file.I assume there was some overwrite/conflict in the test framework when the
setTimeout
s triggered while it was still trying to execute other tests from within the same test file, which caused the test framework to believe it should stop at that test file.