HomeSort by relevance Sort by last modified time
    Searched full:scenario (Results 126 - 150 of 709) sorted by null

1 2 3 4 56 7 8 91011>>

  /packages/apps/Email/tests/src/com/android/email/mail/store/
Pop3StoreUnitTests.java 202 // scenario 1: CAPA returns -ERR, so we try UIDL explicitly
208 // scenario 2: CAPA indicates UIDL, so we don't try UIDL
213 // scenario 3: CAPA returns -ERR, and UIDL fails
377 * Test the scenario where the transport is "open" but not really (e.g. server closed). Two
420 * Test the scenario where the transport is "open" but not really (e.g. server closed). Two
462 * Test the scenario where the transport is "open" but not really (e.g. server closed). Two
505 * Test the scenario where the transport is "open" but not really (e.g. server closed). Two
557 * Test the scenario where the transport is "open" but not really (e.g. server closed). Two
604 * Test the scenario where the transport is "open" but not really (e.g. server closed). Two
663 * Test the scenario where the transport is "open" but not really (e.g. server closed). Tw
    [all...]
  /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/
PerformanceResults.java 37 * configurations and scenario pattern.
162 * @return A list of {@link ScenarioResults scenario results}
175 * @return A list of {@link ScenarioResults scenario results} which have a summary
309 * Get the results of a given scenario.
311 * @param scenarioName The scenario name
312 * @return The {@link ScenarioResults scenario results}
451 * and scenario pattern.
511 * and scenario pattern.
775 // Set scenario pattern default
DB_Results.java 423 * @return The list of all builds names matching the scenario pattern used while reading data
448 * Get component name from a scenario.
450 * @param scenarioName The name of the scenario
471 System.err.println(scenarioName+" does not belongs to a known Eclipse component. So use scenario prefix "+componentName+" as component name by default and add it to the know components"); //$NON-NLS-1$
722 * @return A list of all scenario names matching the default pattern
748 * @return A list of scenario names matching the given pattern
764 * Get all summaries from DB for a given scenario and configuration pattern
766 * @param scenarioResults The scenario results where to store data
776 * Query and store all values for given scenario results
778 * @param scenarioResults The scenario results where the values has to be pu
    [all...]
  /art/test/550-checker-regression-wide-store/smali/
TestCase.smali 25 # Test storing into the high vreg of a wide pair. This scenario has runtime
  /cts/tests/tests/gesture/src/android/gesture/cts/
GestureTest.java 99 // TODO: check scenario where provided Path already has data
  /cts/tests/tests/telecom/src/android/telecom/cts/
CtsRemoteConnectionService.java 67 * created. Used by {@link VideoCallTest#testVideoCallDelayProvider()} to test scenario where
MockConnectionService.java 41 * created. Used by {@link VideoCallTest#testVideoCallDelayProvider()} to test scenario where
  /cts/tests/tests/text/src/android/text/method/cts/
DateKeyListenerTest.java 65 * Scenario description:
DateTimeKeyListenerTest.java 67 * Scenario description:
TimeKeyListenerTest.java 62 * Scenario description:
  /external/autotest/client/site_tests/network_MobileSuspendResume/
network_MobileSuspendResume.py 278 # This is the wrapper around the running of each scenario with
294 logging.info('Checking that modem is powered on after scenario %s.',
298 logging.info('Scenario complete: %s.' % function_name)
336 logging.info('Running scenario group: %s' % scenario_group)
  /external/autotest/contrib/virt/
README 53 use them only as a reference and adapt the examples to your scenario:
  /external/clang/lib/CodeGen/
README.txt 32 performance, and in that scenario we will need to emit the alloca
  /external/curl/tests/libtest/
lib597.c 35 * Test case for below scenario:
  /external/e2fsprogs/lib/ext2fs/
ext3_extents.h 81 * uninitialized extent with only one special scenario when ee_len = 0x8000.
  /external/jacoco/jacoco-maven-plugin/src/org/jacoco/maven/
InstrumentMojo.java 35 * drawbacks and should only be used if a specific scenario explicitly requires
  /external/jacoco/org.jacoco.core.test/src/org/jacoco/core/test/perf/targets/
Target03.java 18 * "Game of Life" implementation as a more reference scenario. Obviously the
  /external/libchrome/sandbox/win/src/sidestep/
preamble_patcher.h 15 // bytes of the function. Considering the worst case scenario, we need 4
  /external/libnfc-nxp/src/
phLlcNfc_StateMachine.c 140 /* Error scenario: There cant be any change in the state,
  /external/mockito/src/org/mockito/internal/util/collections/
HashCodeAndEqualsSafeSet.java 22 * meaning that in this scenario the real code is always called and will most probably
  /external/opencv3/samples/winrt/ImageManipulations/
AdvancedCapture.xaml 34 <TextBlock TextWrapping="Wrap" Grid.Row="0" Text="This scenario shows how to enumerate cameras in the system. Choose a camera from the list to preview, record or take a photo from the chosen camera. You can add the gray scale effect using the checkbox provided." Style="{StaticResource BasicTextStyle}" HorizontalAlignment="Left"/>
  /external/owasp/sanitizer/tools/
update_tree_in_svn.py 95 # scenario.
  /external/parameter-framework/upstream/test/tokenizer/
Test.cpp 44 SCENARIO("Tokenizer tests")
  /external/skia/site/dev/contrib/
index.md 19 We cannot always fix issues or support every scenario, but we welcome any bugs
  /external/toybox/toys/posix/
cal.c 67 // Worst case scenario toybuf usage: sizeof(struct tm) plus 21 bytes/line

Completed in 830 milliseconds

1 2 3 4 56 7 8 91011>>