Bug 224640
| Summary: | Investigate using tox for testing Python code | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Sam Sneddon [:gsnedders] <gsnedders> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ap, don.olmstead, jbedard, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=224638 | ||
| Bug Depends on: | 224869, 226016 | ||
| Bug Blocks: | 261004 | ||
Sam Sneddon [:gsnedders]
c.f. https://tox.readthedocs.io/en/latest/
Whether we care about this probably varies a bit; webkitcorepy etc. are in principle installable via pip so testing them via virtualenvs (therefore in isolated environments) would have some value.
However, the larger value in my book would be able to run tests against multiple supported Python versions in a single command. That said, this is a relatively small benefit compared with the other benefits many get from it.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/76736746>