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

1 2 3 4 5 6 78 91011>>

  /cts/tests/tests/view/src/android/view/cts/
View_FocusHandlingTest.java 141 // test scenario: a view will not actually take focus if it is not focusable
  /development/samples/AppNavigation/res/values/
strings.xml 29 <string name="view_from_other_task_description">This combined demo shows how to handle up navigation when another task has launched your app\'s activity on its own task stack. Navigating up in this scenario should synthesize a task stack representing the most common or direct navigation path to the parent activity. The code example shows how to handle this using helper code from the support library. Press the button below to launch a separate task and begin the demo.</string>
  /development/samples/SupportAppNavigation/res/values/
strings.xml 29 <string name="view_from_other_task_description">This combined demo shows how to handle up navigation when another task has launched your app\'s activity on its own task stack. Navigating up in this scenario should synthesize a task stack representing the most common or direct navigation path to the parent activity. The code example shows how to handle this using helper code from the support library. Press the button below to launch a separate task and begin the demo.</string>
  /external/apache-http/src/org/apache/http/client/methods/
HttpRequestBase.java 156 // deadlocks in the scenario where the callbacks have
  /external/autotest/client/site_tests/policy_CookiesAllowedForUrls/
policy_CookiesAllowedForUrls.py 42 url/host patterns. It also excercises an additional scenario i.e., it
  /external/autotest/client/site_tests/policy_CookiesBlockedForUrls/
policy_CookiesBlockedForUrls.py 42 patterns. It also excercises an additional scenario i.e., it tests that
  /external/autotest/client/tests/ltp/
ltp.py 55 # to specify a custom 'scenario group' which is a comma-separated
  /external/clang/test/CodeGen/
switch-dce.c 125 case 4: // crazy brace scenario
  /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.test.performance.ui/doc/
help.html 100 In this case, a warning icon is shown after the scenario title and flying over it gives the build ID used to compute the variation:</td></tr>
  /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.test.performance.ui/src/org/eclipse/test/performance/ui/
FingerPrintGraph.java 221 // Build each scenario bar graph
370 // - last one is between end of the warning image and the scenario title beginning
375 // No tooltip => delta zone is between end of bar and the scenario title beginning
384 // draw scenario title
RawDataTable.java 25 * Class used to fill details file of scenario builds data.
  /external/icu/icu4c/source/common/unicode/
urep.h 22 * Add usage scenario
  /external/jacoco/org.jacoco.doc/docroot/doc/
offline.html 80 might depend on your deployment scenario. The first instrumented class loaded
  /external/libchrome/base/files/
important_file_writer.cc 217 // using PostTask() in the typical scenario below.
  /external/libchrome/base/posix/
safe_strerror.cc 68 // (but in such a scenario this function is never called). Sadly we can't use
  /external/libchrome/base/synchronization/
condition_variable.h 9 // scenario is that additional tasks are now available for processing. It is
  /external/libnfc-nci/halimpl/pn54x/dnld/
phDnldNfc_Internal.h 76 phDnldNfc_StateTimer, /* State to stop prev set timer on Recv or handle timed out scenario */
  /external/llvm/test/CodeGen/AMDGPU/
lds-output-queue.ll 80 ; This test checks this scenario and makes sure it doesn't result in an
  /external/opencv3/samples/winrt/ImageManipulations/
MainPage.xaml 82 <TextBlock x:Name="ScenarioListLabel" Text="Select Scenario:" Grid.Row="1" Style="{StaticResource SubheaderTextStyle}" Margin="0,5,0,0" />
  /external/opencv3/samples/winrt/JavaScript/
MediaCaptureJavaScript.jsproj 76 <Content Include="sample-utils\scenario-select.html" />
  /external/parameter-framework/upstream/test/functional-tests/
Basic.cpp 65 SCENARIO("Logger should receive info and warnings", "[log]")
  /external/parameter-framework/upstream/test/functional-tests/include/
Test.hpp 42 #define SCENARIO_METHOD(className, ...) TEST_CASE_METHOD(className, "Scenario: " __VA_ARGS__)
  /external/pdfium/testing/
gtest.gyp 102 # implementation. gtest supports this scenario by providing its
  /external/slf4j/jcl-over-slf4j/src/main/java/org/apache/commons/logging/
package.html 113 purposes. A typical scenario for a server application is to have each
  /external/testng/src/main/java/org/testng/reporters/
EmailableReporter2.java 252 * Writes the scenario summary for the results of a given state for a single
293 // Write the timing information with the first scenario per
363 * Writes the scenario details for the results of a given state for a single
391 * Writes the details for an individual test scenario.

Completed in 1717 milliseconds

1 2 3 4 5 6 78 91011>>