c89f64cc7c
Since Buck has no native support for web tests, wrap the tests in a Python shim that calls wct. As in other Polymer cases, we need to prepare a set of inputs and create a directory containing exactly what wct expects to be there. Buck exposes resources to python_tests using the pkg_resources API, which is cumbersome to use, and easier just to ship around zip files as we do elsewhere. Unlike other npm binaries we've encountered, the web-component-tester module has numerous native dependencies, up to and including Selenium. Rather than get in the game of distributing platform-specific binaries, punt and require `wct` to be on the user's $PATH for now. Tests are currently excluded in .buckconfig but can be run directly with either: buck test //polygerrit-ui/app:polygerrit_tests buck test --include web Change-Id: Ia314213925ac27ff271374a96ed539fb2acf0187
34 lines
711 B
Plaintext
34 lines
711 B
Plaintext
[alias]
|
|
api = //:api
|
|
api_deploy = //tools/maven:api_deploy
|
|
api_install = //tools/maven:api_install
|
|
war_deploy = //tools/maven:war_deploy
|
|
war_install = //tools/maven:war_install
|
|
chrome = //:chrome
|
|
docs = //Documentation:searchfree
|
|
firefox = //:firefox
|
|
gerrit = //:gerrit
|
|
headless = //:headless
|
|
polygerrit = //:polygerrit
|
|
release = //:release
|
|
safari = //:safari
|
|
soyc = //gerrit-gwtui:ui_soyc
|
|
soyc_r = //gerrit-gwtui:ui_soyc_r
|
|
withdocs = //:withdocs
|
|
|
|
[buildfile]
|
|
includes = //tools/default.defs
|
|
|
|
[java]
|
|
src_roots = java, resources
|
|
|
|
[project]
|
|
ignore = .git
|
|
|
|
[cache]
|
|
mode = dir
|
|
dir = ~/.gerritcodereview/buck-cache/locally-built-artifacts
|
|
|
|
[test]
|
|
excluded_labels = manual
|