Searched refs:Chrome (Results 1 – 25 of 857) sorted by relevance
12345678910>>...35
/external/autotest/client/site_tests/video_VideoReload/ |
D | control.h264 | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that Chrome can reload mp4 video" 9 This test will fail if Chrome fails to reload mp4 video. 18 'labels': ['OS-Chrome', 'VideoTestFailure'], 23 This test verifies Chrome can reload mp4 video after reloading the page.
|
D | control.vp8 | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that Chrome can reload webm video" 9 This test will fail if Chrome fails to reload webm video. 18 'labels': ['OS-Chrome', 'VideoTestFailure'], 23 This test verifies Chrome can reload webm video after reloading the page.
|
D | control.vp9 | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that Chrome can reload vp9 video" 9 This test will fail if Chrome fails to reload vp9 video. 18 'labels': ['OS-Chrome', 'VideoTestFailure'], 23 This test verifies Chrome can reload vp9 video after reloading the page.
|
/external/autotest/client/site_tests/video_VideoCorruption/ |
D | control.vp8 | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that Chrome can handle corrupted webm video" 9 This test will fail if Chrome fails to catch error for playing corrupted webm video. 18 'labels': ['OS-Chrome', 'VideoTestFailure'], 23 This test verifies Chrome can catch error for playing corrupted webm video.
|
D | control.h264 | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that Chrome can handle corrupted mp4 video" 9 This test will fail if Chrome fails to catch error for playing corrupted mp4 video. 18 'labels': ['OS-Chrome', 'VideoTestFailure'], 23 This test verifies Chrome can catch error for playing corrupted mp4 video.
|
/external/autotest/client/site_tests/documentscan_AppTestWithFakeLorgnette/ |
D | control | 12 This test verifies that the Chrome APIs work correctly to acquire 17 - The extension is unable to interact with the Chrome scanning API 18 - The Chrome scanning API cannot interact with the mock lorgnette 32 within the App. Since the Chrome document scan API requires a user 37 that the Chrome process will communicate with for the purposes of 38 this test. It will accept the D-Bus RPC calls that Chrome makes
|
/external/autotest/client/site_tests/telemetry_AFDOGenerateClient/ |
D | control | 7 PURPOSE = "Navigate a set of pages so that a Chrome profile can be captured" 12 TEST_CLASS = "Chrome AFDO" 17 Run a pre-defined set of pages for the DUT for Chrome profile collection. 20 of pages while a profile of Chrome is captured. It also aims at using 28 build of Chrome.
|
/external/autotest/client/site_tests/network_ProxyResolver/ |
D | control | 5 AUTHOR = "Chrome OS Team" 6 DOC = "Sets a proxy in Chrome and ensures it resolves over DBus" 8 PURPOSE = "Verify Chrome-based proxy resolving works" 9 CRITERIA = "Fails if Chrome returns incorrect or malformed data"
|
/external/autotest/client/site_tests/audio_AudioCorruption/ |
D | control | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that Chrome can handle corrupted mp3 audio" 9 This test will fail if Chrome can't catch error for playing corrupted mp3 audio. 19 This test verifies Chrome can catch error for playing corrupted mp3 audio.
|
/external/autotest/client/site_tests/video_ChromeHWDecodeUsed/ |
D | control.vp9 | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that VP9 video decode acceleration works in Chrome" 9 This test will fail if VDA doesn't work with Chrome navigating to a VP9 webm 21 'labels': ['OS-Chrome', 'VideoTestFailure'],
|
D | control.h264.mse | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that H.264 decode acceleration works for MSE videos in Chrome" 9 This test will fail if VDA doesn't work with Chrome navigating to an MSE mp4 file. 20 'labels': ['OS-Chrome', 'VideoTestFailure'],
|
D | control.h264 | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that H.264 video decode acceleration works in Chrome" 9 This test will fail if VDA doesn't work with Chrome navigating to an mp4 file. 20 'labels': ['OS-Chrome', 'VideoTestFailure'],
|
D | control.vp9.mse | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that VP9 decode acceleration works for MSE videos in Chrome" 9 This test will fail if VDA doesn't work with Chrome navigating to an MSE webm file. 20 'labels': ['OS-Chrome', 'VideoTestFailure'],
|
D | control.vp8 | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that VP8 video decode acceleration works in Chrome" 9 This test will fail if VDA doesn't work with Chrome navigating to a webm file. 20 'labels': ['OS-Chrome', 'VideoTestFailure'],
|
D | control.vp8.mse | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that VP8 decode acceleration works for MSE videos in Chrome" 9 This test will fail if VDA doesn't work with Chrome navigating to an MSE webm file. 20 'labels': ['OS-Chrome', 'VideoTestFailure'],
|
/external/skia/site/dev/sheriffing/ |
D | trooper.md | 43 Valentine passwords and Chrome Golo access are based on membership in this 64 - Machine name ends with "a3", "a4", "m3" -> Chrome Golo 68 - slave11-c3 is a Chrome infra GCE machine (not to be confused with the Skia 72 useful for questions regarding bots managed by the Chrome Infra team and to 81 …[Chrome RDP Extension](https://chrome.google.com/webstore/detail/chrome-rdp/cbkkbcmdlboombapidmoeo… 88 - If there is a problem with a bot in the Chrome Golo or Chrome infra GCE, the 91 with the Chrome infra team. But if you know what you're doing: 92 - To access bots in the Chrome Golo, 98 stored on [Valentine](https://valentine.corp.google.com/) as "Chrome Golo, 100 - To access bots in the Chrome infra GCE -> command looks like `gcutil
|
/external/autotest/client/site_tests/video_VideoSeek/ |
D | control.h264.switchres | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that H264 resolution-changing video seek works in Chrome" 9 This test will fail if a resolution-changing H264 video fails to seek in Chrome HTML5 page. 19 'labels': ['OS-Chrome', 'VideoTestFailure'],
|
D | control.vp8.switchres | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that VP8 resolution-changing video seek works in Chrome" 9 This test will fail if a resolution-changing VP8 video fails to seek in Chrome HTML5 page. 19 'labels': ['OS-Chrome', 'VideoTestFailure'],
|
D | control.h264 | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that H264 non-resolution-changing video seek works in Chrome" 9 This test will fail if a non-resolution-changing H264 video fails to seek in Chrome HTML5 page. 19 'labels': ['OS-Chrome', 'VideoTestFailure'],
|
D | control.vp8 | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that VP8 non-resolution-changing video seek works in Chrome" 9 This test will fail if a non-resolution-changing VP8 video fails to seek in Chrome HTML5 page. 19 'labels': ['OS-Chrome', 'VideoTestFailure'],
|
D | control.vp9 | 5 AUTHOR = "Chrome OS Project, chromeos-video@google.com" 7 PURPOSE = "Verify that VP9 non-resolution-changing video seek works in Chrome" 9 This test will fail if a non-resolution-changing VP9 video fails to seek in Chrome HTML5 page. 19 'labels': ['OS-Chrome', 'VideoTestFailure'],
|
/external/autotest/client/site_tests/video_VideoSanity/ |
D | control.bvt | 5 AUTHOR = 'Chrome OS Project, chromeos-video@google.com' 7 PURPOSE = 'Verify that Chrome media and video works' 9 This test will fail if Chrome media is not enable or video doesn't play. 21 'labels': ['OS-Chrome', 'VideoTestFailure'],
|
/external/skia/site/dev/contrib/ |
D | c++11.md | 22 The clients we pay most attention to are Chrome, Android, Mozilla, and a few 25 Chrome builds with a recent Clang on Mac and Linux and with a recent MSVC on 29 Chrome intentionally disables thread-safe initialization of static variables, 51 bots use a recent toolchain from Android (see above), and our Chrome bots use 52 Chrome's toolchains (see above). I'm not exactly sure what our Chrome OS bots
|
/external/autotest/test_suites/ |
D | control.bvt-cq | 5 AUTHOR = "Chrome OS Team" 17 pass the Chrome OS Commit Queue and Pre-Flight Queue. Test failures 19 * Chrome OS CLs must pass these tests prior to being accepted into 21 * A new Chrome build must pass these tests prior to the build 22 being included in a Chrome OS canary build.
|
/external/autotest/client/site_tests/security_BundledExtensions/ |
D | baseline | 5 # Chrome Web Store ("ahfgeienlihckogmohjhadlkjgocpleb"), 9 # already tracked and reviewed on the Chrome side. Ignore them 57 "name": "Chrome Goodies", 66 "name": "Chrome", 167 { "name": "Chrome OS text-to-speech component extension",
|
12345678910>>...35