I probably won't attend, but I'd like the adoption of a unified JS API
for declaring and running tests to be discussed. tl;dr see bug 867742
for one possible approach.
This would facilitate simplicity throughout:
* Tests would be written in a consistent format, decreasing cognitive
load to write tests. Developers would write tests faster.
* Tests would have a common API of shared components to draw from. Spend
less time writing test code and more time leveraging using existing
libraries/helpers.
* Python code for invoking tests would be simpler.
* It would be easier to move tests between harnesses (since tests are
written in a common format).
I don't know about others, but I often find myself spending more time
writing tests for JS-based features than I do the code being tested. I
view the differences between test environments and the lack of a strong
culture around writing reusable and extensible testing code as
significant factors contributing to that. I strongly believe that
establishing a unified JS API for declaring and writing JS tests that is
based on a modules-first mentality would drastically reduce the overhead
for writing and maintaining tests and would enable JS developers to move
faster.
On 11/26/14 10:43 AM, David Rajchenbach-Teller wrote:
Well, I do not have a specific program, but something along the lines of:
1. What has changed recently and why.
- (mdeboer?) Assert.jsm.
- (me) Uncaught rejections as failures.
- Treeherder
2. What are the itches with the current state of test suites?
- (me) Warnings-as-noise (yes, it's testsuite-related).
3. How can we fix them.
- (me) Warnings-as-actionable-issues.
Cheers,
David
On 26/11/14 17:11, Ehsan Akhgari wrote:
On 2014-11-26 6:01 AM, David Rajchenbach-Teller wrote:
The test suites have changed a lot during the past few months (e.g.
Assert.jsm, fail-on-uncaught-rejections), and as I have exposed on
dev-platform, I have plans to further change them.
If you are attending MozLandia and want to brainstorm future changes on
the test suites, please ping me so that we can arrange a session.
Can you please list the changes that you're looking to discuss in the
session? I think that will help people get a sense of whether they
would like to attend. :-)
Thanks!
Ehsan
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
