Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit b9a5b78d authored by David Saff's avatar David Saff
Browse files

Remove stale e2e test mapping info from unit TEST_MAPPING file 

Bug: 319890473
Test: N/A
Flag: TEST_ONLY

Change-Id: I5ac3f2936d4d05ba007e21c84b109655b2fec438
parent 0143339b

packages/SystemUI/TEST_MAPPING

+2 −18
Original line number Diff line number Diff line 
{

  // Curious where your @Scenario tests are running?

  //

  // @Ignore: Will not run in any configuration

  //

  // @FlakyTest: Tests that don't block pre/postsubmit but are staged to run known failures.

  //             Tests will run in postsubmit on sysui-e2e-staged suite.

  //

  //

  // @PlatinumTest: Marking your test with this annotation will put your tests in presubmit.

  //                Please DO NOT annotate new or old tests with @PlatinumTest annotation

  //                without discussing with mdb:android-platinum

  //

  // @Postsubmit: Do not use this annotation for e2e tests. This won't have any affect.



  // For all other e2e tests which are not platinum, they run in sysui-silver suite,that

  // primarily runs in postsubmit with an exception to e2e test related changes.

  // If you want to see one shot place to monitor all e2e tests, look for

  // sysui-e2e-staged suite.

  // Test mappings for SystemUI unit tests.

  // For e2e mappings, see go/sysui-e2e-test-mapping



  // v2/android-virtual-infra/test_mapping/presubmit-avd

  "presubmit": [