/test/vti/dashboard/src/main/webapp/WEB-INF/jsp/ |
D | show_release.jsp | 39 …<a class="${testType == 'plan' ? 'active' : 'inactive'}" href="${requestScope['javax.servlet.forwa… 49 …set var="typeParam" scope="session" value="${testType == 'suite' ? '&type=suite' : '&type=plan'}"/> 51 <c:forEach items='${planNames}' var='plan'> 55 <a href='/show_plan_release?plan=${plan}${typeParam}'> 57 <span class='entry valign'>${plan}</span> 62 …<a href='/show_green_release?plan=${plan}${typeParam}' class="waves-effect waves-light btn">Green<… 67 <a href='/show_plan_release?plan=${plan}${typeParam}'> 69 <span class='entry valign'>${plan}</span>
|
D | show_plan_release.jsp | 42 search = $('#filter-bar').createSearchHeader('Plan: ', '${plan}', refresh); 70 '/show_plan_release?plan=${plan}&endTime=' + endTime + 83 '/show_plan_release?plan=${plan}&startTime=' + startTime + 94 '/show_plan_release?plan=${plan}' + search.args();
|
D | show_green_plan_release.jsp | 39 <h4 id="test-plan-section-header">Test Plans</h4> 42 <div class='row' id='test-plan-green-release-container'> 65 … <a href="/show_plan_run?plan=${plan}&time=${deviceBuildInfo.candidateBuildIdTimestamp}"> 84 … <a href="/show_plan_run?plan=${plan}&time=${deviceBuildInfo.greenBuildIdTimestamp}">
|
D | show_suite_release.jsp | 121 <b>Plan: </b><span><c:out value="${plan}"></c:out></span> 164 …></c:out>" href="${requestScope['javax.servlet.forward.servlet_path']}?plan=${plan}&type=${testTyp… 167 …></c:out>" href="${requestScope['javax.servlet.forward.servlet_path']}?plan=${plan}&type=${testTyp… 170 …></c:out>" href="${requestScope['javax.servlet.forward.servlet_path']}?plan=${plan}&type=${testTyp… 327 …<a href="${requestScope['javax.servlet.forward.servlet_path']}?plan=${plan}&type=${testType}&testC… 338 …<a href="${requestScope['javax.servlet.forward.servlet_path']}?plan=${plan}&type=${testType}&testC… 346 …<a href="${requestScope['javax.servlet.forward.servlet_path']}?plan=${plan}&type=${testType}&testC…
|
D | show_green_suite_release.jsp | 43 <div class='row' id='test-plan-green-release-container'>
|
D | show_plan_run.jsp | 137 // Draw a test plan run summary box.
|
/test/vts-testcase/fuzz/script/config/ |
D | config_gen.py | 120 plan = 'vts-staging-fuzz' 124 plan = old_plans[0] 132 hal_name, hal_version, fuzzer_type, plan, bp_template) 135 hal_name, hal_version, fuzzer_type, plan, xml_template) 187 def _FillOutTemplate(self, hal_name, hal_version, fuzzer_type, plan, argument 210 config = config.replace('{PLAN}', plan)
|
/test/mts/tools/mts-tradefed/ |
D | README | 21 To run a test plan on a single device: 29 'run mts' to run the default MTS plan 39 To shard a plan test run on multiple devices
|
/test/vts/tools/vts-tradefed/res/config/ |
D | plans.md | 3 A VTS test plan consists of a set of VTS tests. Typically the tests within a 4 plan are for the same target component or testing the same or similar aspect 27 name of a serving plan always starts with 'vts-staging-'.
|
/test/vts/tools/vts-core-tradefed/ |
D | README | 36 To run a test plan on a single device: 46 'run vts' to run the default VTS plan 56 To shard a plan test run on multiple devices
|
/test/suite_harness/tools/cts-tradefed/ |
D | README | 38 To run a test plan on a single device: 48 'run cts' to run the default CTS plan 58 To shard a plan test run on multiple devices
|
/test/suite_harness/common/util/src/com/android/compatibility/common/util/ |
D | InvocationResult.java | 150 public void setTestPlan(String plan) { in setTestPlan() argument 151 mTestPlan = plan; in setTestPlan()
|
D | LightInvocationResult.java | 153 public void setTestPlan(String plan) { in setTestPlan() argument 154 mTestPlan = plan; in setTestPlan()
|
D | IInvocationResult.java | 51 void setTestPlan(String plan); in setTestPlan() argument
|
/test/vti/dashboard/ |
D | README.md | 114 http://127.0.0.1:8080/api/test_data/plan 123 First, in test-plan-report-data.json, you need to set the same number of data under "testCaseNames" 172 test-plan-report-data.json 197 curl -d @testdata/test-plan-report-data.json -m 30 -X POST http://127.0.0.1:8080/api/test_data/plan…
|
/test/suite_harness/common/host-side/tradefed/tests/src/com/android/compatibility/common/tradefed/result/ |
D | SubPlanHelperTest.java | 115 ISubPlan plan = mSubPlanHelper.createSubPlan(mBuildHelper); in testCreateSubPlan() local 116 Set<String> planIncludes = plan.getIncludeFilters(); in testCreateSubPlan() 117 Set<String> planExcludes = plan.getExcludeFilters(); in testCreateSubPlan()
|
/test/vts/testcases/vts_selftest/test_framework/python_virtualenv_preparer_test/ |
D | README.md | 10 …er a python module installed in previous tests is still available through plan level virtual envir…
|
/test/vti/dashboard/src/main/java/com/android/vts/servlet/ |
D | ShowPlanRunServlet.java | 71 String plan = request.getParameter("plan"); in doGetHandler() local 93 Key planKey = KeyFactory.createKey(TestPlanEntity.KIND, plan); in doGetHandler()
|
/test/vti/dashboard/src/main/webapp/css/ |
D | plan_runs.css | 19 .release-entry .plan-run-metadata {
|
/test/vts/proto/ |
D | VtsReportMessage.proto | 329 // this plan. 333 // The test plan name. 340 // Only used for profiling test plan.
|
/test/vti/test_serving/proto/ |
D | GreenBuildScheduleConfigMessage.proto | 45 // To specify a test plan scheduling policy.
|
/test/vts/doc/ |
D | user_manual.md | 78 ### <a name="run_vts" /> 2.1. Run a VTS test plan
|