Skip to content

Update upm project dependency com.unity.test-framework to v1.4.6 #347

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

unity-renovate[bot]
Copy link

This PR contains the following updates:

Package Type Update Editor Change
com.unity.test-framework dependencies minor ✅ Compatible 1.1.31 -> 1.4.6
com.unity.test-framework dependencies minor ✅ Compatible 1.1.33 -> 1.4.6

✅ Editor bump: Not required for TestProjects/Main/Packages/manifest.json

This is probably safe to merge for this project

✅ Editor bump: Not required for TestProjects/AutomatedTests/Packages/manifest.json

This is probably safe to merge for this project


Release Notes

com.unity.test-framework (com.unity.test-framework)

v1.4.6

Compare Source

  • Fixed an issue where the architecture flag would not be parsed for the StandaloneOSX platform.
  • Fixed an issue where the test results ui and progress bar would not update before a user input, such as mouse movement, was detected (UTF-609).
  • Fixed an issue where root of the test tree was marked as NotRun, when all the tests were run and at least one test is ignore.
  • Ensure that an error is raised and the test run is stopped if a playmode test method exits playmode (DSTR-1091).
  • Async editmode tests are no longer throw error when yielding a different value than null (DSTR-1066)
  • Fixed an issue where the "C# Test Script" button was always disabled in One Column view in Project tab. (DSTR-1083)
  • Async and UnityTest can now use ParametrizedIgnore attribute. (DSTR-1068)
  • Corrected Timeout to only apply to the test method and not the teardown methods, ensuring that TearDown is always run if a test case times out (DSTR-1077).
  • Added a queue size indicator in the player side test result ui. This can be used to track the progress of sending back result data to the editor.
  • Parent node of the test tree is now updated after all children finish running and have a result.

v1.4.5

Compare Source

  • Fixed an issue where batchmode test runs would never finish if a test yielded WaitForEndOfFrame (DSTR-1009).
  • Fixed an issue where the location prompt was required when using the Install all tests in 'build' folder option during test builds.
  • Canceling a PlayMode test run now correctly restores the scene setup, instead of leaving the editor in the test scene.
  • Fixed an issue where UnitySetUp did not fail when nested coroutines threw an exception (DSTR-1007).
  • When selecting multiple tests and running them, the test runner now correctly updates the details of the first selected test (UTF-602).
  • The interaction mode and application idle time settings is now being changes when running tests, resulting in faster test runs if not already in use (applies to 2020.3 and later) (DSTR-690).
  • Fixed an issue where some NUnit attributes caused errors and stopped async test runs (DSTR-1040).
  • Added support for the MaxTime attribute on async and UnityTest methods (DSTR-1040).
  • Fixed a memory leak issue where a large number of domain reloads within the same test could crash the editor (DSTR-1023).
  • Changed to use a progress bar inside the test runner window when running tests. This ensures that the progress bar is not fighting to display when e.g. compiling scripts and also makes it easier to cancel a run. This progress bar is displayed for all types of runs (EditMode, PlayMode and Player). (UTF-596).
  • Fixed an issue where ignored tests with an attributes did not display the ignore reason in the test runner UI.
  • Having multiple tests with the same unique id no longer gives a error with 'An item with the same key has already been added', but instead logs an warning about the duplicate id.
  • The result icons for test suites should no longer flicker when running tests.
  • Ensured that test results ignored in the editor but run on a player are not overwritten with ignore status when shown in the UI (DSTR-1042).
  • Fixed an issue where the RunStarted event was not invoked correctly during a test run (DSTR-1046).
  • Fixed an issue where TestStarted and TestFinished events were repeated for ignored test fixtures after a domain reload (DSTR-986).

v1.4.4

Compare Source

  • Fix the issue where playmode controller wasn't being set and cleaned up correctly, causing issues post test run. (DSTR-1025)
  • Fixed an issue where Oculus Quest headsets might timeout before the test run starts (DSTR-404).
  • Fixed a regression where the console output would no longer get attached to the test result for PlayMode.

v1.4.3

Compare Source

  • Fixed a performance issue in relation to the new ui, where running a large selection of tests did not perform well. (DSTR-983)
  • The test tree no longer is fully expanded when the window is first opened, fixing test tree explosion. (DSTR-985)
  • Fixed an issue in Solution 13 of Samples where the path was pointing to a wrong location. (DSTR-1005)
  • Updated documentation of Solution 13 of Samples to reflect more accurate solution for the example. (DSTR-1005)
  • Added ability to build all or selected tests from test runner UI. (UTF-553)

v1.4.2

Compare Source

  • Issue where playmode tests were not recording test results correctly after the first run was fixed. (DSTR-984)
  • A timeout message is now printed when the test failures occurs before the test finishes. (DSTR-476)
  • Nested enumerators are now having their first step executed in the same frame as the parent enumerator. (DSTR-888)
  • Fixed an issue where test projects without PlayMode tests would give the error "No callbacks received." when running in batchmode on some Unity versions.

v1.4.1

Compare Source

  • Multiple improvements to the UI, including better dropdowns, filtering, and a new test list view for Player.
  • Fixed uncategorized UI tests filtering for parameterized tests (DSTR-219).
  • In async tests, any failing logs will now first be evaluated after the async method has completed. (DSTR-839)

v1.4.0

Compare Source

  • Added api for saving test results to a file.
  • Added a button for saving the test results of the latest run.
  • Applied filtering to the ITestAdaptor argument of ICallbacks.RunStarted so that it corresponds to the actual test tree being run.
  • When running in player:
    • the save scene dialog is shown when there are changes in the scene.
    • the scene setup is restored after a completed run.
  • When running in playmode:
    • the scene setup is restored after a completed run.
  • Added overloads of LogAssert.Expect which allow users to expect a log message without specifying a severity, which will match logged messages of any severity.
  • Added new [ParametrizedIgnore] attribute which allows ignoring tests based on arguments which were passed to the test method.
  • Added a new PreservedValuesAttribute to allow for using the nunit ValuesAttribute at players with a high stripping level (case DSTR-33).
  • Added api for canceling test runs.

v1.3.9

Compare Source

  • By using the editor command line new argument -randomOrderSeed x you can run the tests in a randomized order, where x is an integer different from 0. If a new test is added in the project the random order passing the same seed will be kept, and the new test will be placed in the random list accordigly.
  • Fix for WebGL platform target to close the browser tab when the run is completed.
  • Added TestFileReferences.json to be generated on build step of the player, so can be consumed later by Test runners to enrich data for run part.

v1.3.8

Compare Source

  • By using the editor command line new argument -randomOrderSeed x you can run the tests in a randomized order, where x is an integer different from 0. If a new test is added in the project the random order passing the same seed will be kept, and the new test will be placed in the random list accordigly.
  • Fix for WebGL platform target to close the browser tab when the run is completed.
  • Added TestFileReferences.json to be generated on build step of the player, so can be consumed later by Test runners to enrich data for run part.

v1.3.7

Compare Source

  • By using the editor command line new argument -randomOrderSeed x you can run the tests in a randomized order, where x is an integer different from 0. If a new test is added in the project the random order passing the same seed will be kept, and the new test will be placed in the random list accordigly.
  • Fix for WebGL platform target to close the browser tab when the run is completed.
  • Added TestFileReferences.json to be generated on build step of the player, so can be consumed later by Test runners to enrich data for run part.

v1.3.5

Compare Source

  • It’s now possible to retry and repeat tests on test level, meaning as soon as the test finishs running the first iteration, we now retry or repeat it. Command line arguments to pass to the Editor:
    • -repeat x runs the test x amount of times or until it fails. It is useful for testing unstable tests
    • -retry x if a test fails, run that test x amount of times or until it succeeds.
  • Fixed various documentation bugs reported via the docs user feedback system.
  • Fixed TestMode not being set correctly on root level of test tree (DSTP-674).
  • It's now possible to select browser for running WebGL player tests in player settings. (DSTR-811)

v1.3.4

Compare Source

  • Fixes output message concurrency issue with async Setup.
  • Fixed multiple issues where tests would not time out, when running longer than the default timeout or the timeout defined in a TimeoutAttribute (DSTR-607).
  • Added UNITY_TEST_FRAMEWORK define constraint to filter out test framework assemblies from normal platform and asset bundle builds. (DSTR-791)
  • Ensured that all playmode tests have a disabled splashscreen and unity logo by default if Unity license permits such action.
  • Added strictDomainReload feature to enable cheching for pending domain reloads/compilations at the end of managed tests (DSTR-793).

v1.3.3

Compare Source

  • Fixes an issue where a test body would be skipped under certain conditions regarding domain reload.
  • Fixed an issue where the "uncategorized" category filter would not apply correctly to parameterized tests with a category in the fixture (DSTR-700).
  • Ensured that all samples can be loaded at once without assembly name collisions.

v1.3.2

Compare Source

No release notes found for this version

v1.3.1

Compare Source

No release notes found for this version

v1.3.0

Compare Source

No release notes found for this version

v1.1.33

Compare Source

  • Fixed an issue where using Assert.Expect with the same string multiple times can lead to incorrect errors in some cases (DSTR-442).
  • Improved the logging when using multiple Assert.Expect that the logs appear in another order than expected (DSTR-442).
  • Moved the targetPlatform specified when running tests in the TestRunnerApi from the Filter to the ExecutionSettings (DSTR-186).
  • Fixed an issue where an inheritance of UnityPlatformAttribute which was not working (ESTT-70).
  • Fixed the log of excluded platforms which was not displaying the right information.
  • Added filename and linenumber to test finished message (DSTR-505).
  • Add the possibility of running tests in a specified order from a test list (DSTR-494).

v1.1.31

Compare Source

No release notes found for this version


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Unity Renovate Bot.

@unity-renovate
Copy link
Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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.

0 participants