| /art/test/131-structural-change/ |
| info.txt | 1 Check whether a structural change in a (non-native) multi-dex scenario is detected.
|
| /external/caliper/caliper/src/main/java/com/google/caliper/model/ |
| Trial.java | 32 * An invocation of a single scenario measured with a single instrument and the results thereof.
42 private Scenario scenario; field in class:Trial
49 this.scenario = Scenario.DEFAULT;
57 this.scenario = builder.scenario;
73 public Scenario scenario() { method in class:Trial
74 return scenario;
114 private Scenario scenario; field in class:Trial.Builder
139 public Builder scenario(Scenario.Builder scenarioBuilder) { method in class:Trial.Builder
143 public Builder scenario(Scenario scenario) { method in class:Trial.Builder
[all...] |
| Scenario.java | 34 public final class Scenario {
35 static final Scenario DEFAULT = new Scenario();
44 private Scenario() {
50 private Scenario(Builder builder) {
71 } else if (obj instanceof Scenario) {
72 Scenario that = (Scenario) obj;
137 public Scenario build() {
141 return new Scenario(this)
[all...] |
| /external/opencv3/samples/winrt/ImageManipulations/ |
| Constants.cpp | 17 Platform::Array<Scenario>^ MainPage::scenariosInner = ref new Platform::Array<Scenario>
20 // { "Description for the sample", "Fully quaified name for the class that implements the scenario" }
|
| Constants.h | 16 public value struct Scenario
33 static property Platform::Array<Scenario>^ scenarios
35 Platform::Array<Scenario>^ get()
41 static Platform::Array<Scenario>^ scenariosInner;
|
| /external/opencv3/samples/winrt/JavaScript/sample-utils/ |
| scenario-select.html | 9 <h3 id="listLabel">Select scenario:</h3>
11 <!-- scenario list is inserted here -->
|
| /frameworks/native/cmds/flatland/ |
| README.txt | 28 in between each benchmark sample run. Regardless of the scenario being
38 Scenario | Resolution | Time (ms)
49 The first column is simply a description of the scenario that's being
50 simulated. The second column indicates the resolution at which the scenario
53 scenario takes to complete.
57 fast - This indicates that frames of the scenario completed too fast to be
60 result, the scenario was skipped.
62 slow - This indicates that frames of the scenario took too long to
64 simulating a scenario that is obviously impractical on this device, the
65 scenario was skipped
[all...] |
| /external/jacoco/org.jacoco.core.test/src/org/jacoco/core/test/perf/ |
| IPerfScenario.java | 15 * Interface for a performance scenario.
20 * Runs the performance scenario and reports the result to the given
|
| /external/parameter-framework/upstream/test/functional-tests/ |
| plan.md | 5 in this same BDD format in order to check scenario coverage.
7 - If a scenario does not specify a config files,
36 - [X] Scenario: Default logger
40 - [X] Scenario: No logger
44 - [X] Scenario: Logger should receive info and warnings
51 - [X] Scenario: Unset logger
61 - [ ] Scenario: Tuning OK
66 - [ ] Scenario: Invalid tunning
71 - [ ] Scenario: Forbiden invalid tunning
77 - [ ] Scenario: Plugin O
[all...] |
| /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.test.performance.ui/images/ |
| descriptions.html | 12 <p><a name="sst"></a><font size="+2"><b>Scenario Status Table Example</b></font></p>
15 <p><a name="sr"></a><b><font size="+2">Scenario Results Example</font></b></p>
|
| /external/mockito/src/org/mockito/internal/exceptions/util/ |
| ScenarioPrinter.java | 29 String scenario = sb.toString();
local
30 return scenario;
|
| /external/autotest/tko/parsers/test/templates/ |
| scenario_package_common.py | 1 # This is meant to run from within a scenario package
|
| /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.test.performance.ui/ |
| contexts.xml | 5 + Scenario
10 Typically, the Eclipse builder runs performance tests for each component after the build is made on several performance test machines. Each component defines one or several specific performance test suites made of several test (aka scenario). Several performance numbers (e.g. Elapsed Process Time and CPU Time) are stored for each scenario and all build results are available in the performance results database.
27 a table where each column represents a scenario and each line a build.
|
| /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.test.performance.ui/src/org/eclipse/test/performance/ui/ |
| Main.java | 30 * <li>A global php file including global scenario fingerprints and links for all concerned components results php files</li>
31 * <li>A php file for each component including scenario fingerprints and status table with links to a scenario data file</li>
32 * <li>A data HTML file for each config of each scenario included in status table</li>
|
| /external/guava/guava-gwt/test-super/com/google/common/collect/super/com/google/common/collect/ |
| OrderingTest.java | 848 Scenario<T> starter = new Scenario<T>((Ordering) ordering, list, emptyArray);
852 private static <T> void verifyScenario(Scenario<T> scenario, int level) {
853 scenario.testCompareTo();
854 scenario.testIsOrdered();
855 scenario.testMinAndMax();
856 scenario.testBinarySearch();
857 scenario.testSortedCopy();
861 verifyScenario(alteration.mutate(scenario), level + 1)
[all...] |
| /external/guava/guava-tests/test/com/google/common/collect/ |
| OrderingTest.java | 882 Scenario<T> starter = new Scenario<T>((Ordering) ordering, list, emptyArray);
886 private static <T> void verifyScenario(Scenario<T> scenario, int level) {
887 scenario.testCompareTo();
888 scenario.testIsOrdered();
889 scenario.testMinAndMax();
890 scenario.testBinarySearch();
891 scenario.testSortedCopy();
895 verifyScenario(alteration.mutate(scenario), level + 1)
[all...] |
| /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.test.performance.ui/html/ |
| components.html | 26 or several specific performance test suites made of several test (aka scenario).
29 for each scenario and all build results are available in the performance results
35 + Scenario
47 The red cross means that there's at least one scenario on one machine for
65 Note that for component and scenario level, the status is the aggregation of
66 the children status. That means that as soon as one scenario is in error then
89 scenario, hence the corresponding filter is also activated by default.
|
| /external/parameter-framework/upstream/tools/clientSimulator/ |
| README.md | 34 allows writing scenario, mixing criterion changes and arbitrary script
53 * `-s`, `--scenario` : precise the scenario number to launch
63 The script will wait for a choice and the desired scenario will be
64 launched. You can also directly select a scenario with -`s` option.
82 - The path to the directory containing the scenario files.
118 ### Scenario
120 All scenario files need to be put in the directory mentioned by the
123 A scenario file contains all the actions you want to take. *Note*: it is an
147 This scenario file sets a criterion, then runs a script, then sets thre
[all...] |
| pfClientSimulator.py | 36 from clientsimulator.scenario.Scenario import Scenario
83 Scenario(consoleLogger,
89 logger.info("Scenario execution complete.")
101 parser.add_argument("-s", "--scenario", type=int, default=None, nargs='+',
107 " implicit if neither '--scenario' nor '--interactive' are "
203 if args.scenario is not None:
204 for elem in args.scenario:
206 if (args.scenario is None) or args.no_exit
[all...] |
| /external/autotest/tko/parsers/test/ |
| new_scenario.py | 2 """Create new scenario test instance from an existing results directory.
16 While much is done automatically, a scenario harness is meant to
31 help='Name for new scenario instance. Will use dirname if not specified')
39 help='Type of unittest module to copy into new scenario.')
69 'Scenario package already exists at path: %s' %
74 # Create new scenario package
|
| /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.test.performance.ui/src/org/eclipse/test/internal/performance/results/db/ |
| SQL_Results.java | 96 * Query all scenarios corresponding to the default scenario pattern
104 String statement = "select distinct SCENARIO.ID, SCENARIO.NAME , SCENARIO.SHORT_NAME from SCENARIO where " + //$NON-NLS-1$
105 "SCENARIO.NAME LIKE ? " + //$NON-NLS-1$
106 "order by SCENARIO.NAME"; //$NON-NLS-1$
114 * Query all scenarios corresponding to a given scenario pattern
124 String statement = "select distinct SCENARIO.ID, SCENARIO.NAME , SCENARIO.SHORT_NAME from SCENARIO, SAMPLE, VARIATION where " + //$NON-NLS-1
[all...] |
| ScenarioResults.java | 27 * Class to handle performance results of a component's scenario
30 * It gives access to results for each configuration run on this scenario.
127 * related to this scenario. This name does not contain the extension.
133 this.fileName = "Scenario" + this.id; //$NON-NLS-1$
139 * Returns the scenario label. If no label exist as there's no associated summary,
142 * @return The label of the scenario or it's short name if no summary exists
149 * Returns the short name of the scenario. Short name is the name scenario
152 * @return The scenario short name
204 * Returns whether one of the scenario's config has a summary or not
[all...] |
| /external/autotest/client/tests/kvm/ |
| README | 5 scenario:
|
| /external/caliper/caliper/src/main/resources/ |
| CaliperCore.gwt.xml | 13 <include name="**/Scenario.java"/>
|
| /external/parameter-framework/upstream/tools/clientSimulator/clientsimulator/scenario/ |
| Scenario.py | 33 class Scenario:
37 to play a complete scenario.
51 :param scenarioFileName: name of file containing scenario description
84 Parse actions from a scenario.
87 :param scenarioFileName: name of file containing scenario description
92 :return: parsed scenario's actions with system-known types
129 # are directly writed in the scenario's file
166 Execute a Scenario
|
