Separate Functional and Unit Test Modes #166
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.
Producing the unit and functional test bundles in the same mode (
test
) is problematic, as there is no way to ensure that only theunit.js
andfunctional.js
files need would be created. The build would on non-legacy builds (depending on configuration and project code) create extra bundles meaning that neither theunit.js
orfunctional.js
bundle would be correct and would cause the test commands to fail.These changes introduce two new modes
unit
andfunctional
to the build command that provide explicit instructions on which bundle is needed and enables the build to ensure there is always only a single output bundle produced.The existing
test
mode has been deprecated and will only produce theunit
bundle now and produce a warning to consumers about moving to theunit
orfunctional
modes.Limited support for the
test
mode will be removed in the major release after 4.0.0. Thetest
mode will continue to product theunit
bundle as this is the most common usage.