So that it no longer has to be kept in the Engine Content folder.īecause of this change, the type of test being created will dictate where it should be stored. This also means that since these tests are located in plugins, you can choose to include them with your packaged builds when you compile. These have now been moved to their own plugins thatĬan be individually enabled. This enables your QA testing to quickly compare screenshots to identify potential rendering issues between versions or builds.įor a long time, automation tests were spread across the Engine and Editor which meant that when you shipped your title, these were included. See EditorAutomationTests.cpp or EngineAutomationTests.cpp for examples of these. Automated testing is the application of software tools to automate a human-driven manual process of reviewing and validating a software product. More thorough testing of a particular system to avoid crashes, such as loading all maps or loading and compiling all Blueprints. Only mark Unit Tests or fast Feature Tests as Smoke Tests. ![]() All Smoke tests are intended to complete within 1 second.
0 Comments
Leave a Reply. |