![]() For test classes used across multiple directories, it might make sense to move them into a nested test namespace for clarity. For example, see //mojo/core/core_ and //mojo/core/test/mojo_test_. While test files generally appear alongside the production code they test, support code for testonly targets should be placed in a test/ subdirectory.Tests can depend on such targets, but production code can not. Classes used only for testing should be in a GN build target that is marked testonly=true. ![]() These suffixes are checked at presubmit time to ensure the functions are called only by test files. ForTesting is the conventional suffix although similar patterns, such as ForTest, are also accepted.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |