This repository has been archived by the owner on Apr 3, 2019. It is now read-only.
Test Error: Firefox Desktop Sync reset password - TypeError: Cannot read property 'headers' of undefined #1690
Assignees
Comments
shane-tomlinson
pushed a commit
that referenced
this issue
Oct 7, 2014
…tate and when loading emails. fixes #1690
shane-tomlinson
pushed a commit
that referenced
this issue
Oct 10, 2014
Several problems: * When running against remote servers, Selenium moves very quickly. * The email index being searched for was not being passed to restmail, so it would return as long as one email existed. * OAuth tests depended on each other * Signing out of 123done was not done correctly and state would hang around. * Clearing content server state was being done before the content server was loaded, which ended up in a 500 error. What we do now: * Simplify the OAuth sign in tests so there is no cross-test dependencies. * In the OAuth sign in tests, use the FxaClient to pre-generate users. We are testing sign in, not sign up. * Ensure the content server page is loaded before clearing its state. * Ensure the user is logged out of 123done when clearing its state - do so by calling XHR requests directly. * Ensure the index of the email we are waiting for makes it to restmail. fixes #1690
shane-tomlinson
pushed a commit
that referenced
this issue
Oct 10, 2014
Several problems: * When running against remote servers, Selenium moves very quickly. * The email index being searched for was not being passed to restmail, so it would return as long as one email existed. * OAuth tests depended on each other * Signing out of 123done was not done correctly and state would hang around. * Clearing content server state was being done before the content server was loaded, which ended up in a 500 error. What we do now: * Simplify the OAuth sign in tests so there is no cross-test dependencies. * In the OAuth sign in tests, use the FxaClient to pre-generate users. We are testing sign in, not sign up. * Ensure the content server page is loaded before clearing its state. * Ensure the user is logged out of 123done when clearing its state - do so by calling XHR requests directly. * Ensure the index of the email we are waiting for makes it to restmail. fixes #1690
shane-tomlinson
pushed a commit
that referenced
this issue
Oct 10, 2014
Several problems: * When running against remote servers, Selenium moves very quickly. * The email index being searched for was not being passed to restmail, so it would return as long as one email existed. * OAuth tests depended on each other * Signing out of 123done was not done correctly and state would hang around. * Clearing content server state was being done before the content server was loaded, which ended up in a 500 error. What we do now: * Simplify the OAuth sign in tests so there is no cross-test dependencies. * In the OAuth sign in tests, use the FxaClient to pre-generate users. We are testing sign in, not sign up. * Ensure the content server page is loaded before clearing its state. * Ensure the user is logged out of 123done when clearing its state - do so by calling XHR requests directly. * Ensure the index of the email we are waiting for makes it to restmail. fixes #1690
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Running against latest using
npm run test-latestfrom this PR: #1689This is strange because all other tests that use emails passed.
The text was updated successfully, but these errors were encountered: