Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimizing functional test suite with separating auth and non-auth tests #711

Closed
karlcow opened this issue Sep 28, 2015 · 0 comments
Closed

Comments

@karlcow
Copy link
Member

karlcow commented Sep 28, 2015

We want to optimize our test suites: two sets of files requiring authentification and not.

For example:

  • issues-auth.js
  • issues-non-auth.js

This will help us further down the line with optimization.

Steps:

  1. Separate files
  2. Add setup/teardown

Decided in webcompat meeting in Paris September 2015 - @miketaylr

@karlcow karlcow added this to the Paris Meeting September 2015 milestone Sep 28, 2015
miketaylr pushed a commit that referenced this issue Sep 28, 2015
-auth.js is for tests that use logged in state.
-non-auth.js is for tests that don't.
miketaylr pushed a commit that referenced this issue Sep 28, 2015
miketaylr pushed a commit that referenced this issue Oct 1, 2015
-auth.js is for tests that use logged in state.
-non-auth.js is for tests that don't.
miketaylr pushed a commit that referenced this issue Oct 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants