-
Notifications
You must be signed in to change notification settings - Fork 27
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
Failing browser tests #326
Comments
A clarification: The There is a much smaller program test fixture that provides a single school object and a program object carrying the |
@higs4281 thanks! This fixes some of the tests, although there are still some that fail:
So at a minimum we'll want to update the testing instructions to add a Unfortunately, while some of the errors seem maybe to be due to logic timing ( |
I don't think #285 would have affected tests. I'll have to get more familiar with the tests. |
The JavaScript functional (browser) tests documented here currently fail with numerous errors.
At first glance this appears to be due to a mismatch between the test data and the browser tests. For example, the browser tests load this local page:
http://localhost:8000/paying-for-college2/understanding-your-financial-aid-offer/offer/?iped=408039&pid=981&oid=f38283b5b7c939a058889f997949efa566c616c5&totl=45000&tuit=38976&hous=3000&book=650&tran=500&othr=500&pelg=1500&schg=2000&stag=2000&othg=100&ta=3000&mta=3000&gib=3000&wkst=3000&parl=14000&perl=3000&subl=15000&unsl=2000&ppl=1000&gpl=1000&prvl=3000&prvi=4.55&prvf=1.01&insl=3000&insi=4.55&inst=8
(note
pid=981
)When this page is loaded, this error message is displayed instead of a functional page:
The test data (which can be loaded with
./manage.py loaddata collegedata
) does not include a program withprogram_code=981
, so it fails the test here.Looking back in the git history for this repo, the browser tests were last updated in #248 on August 4, 2016. The test data was last updated in #285 on October 11, 2016. Perhaps the tests were not updated when the test data was -- if so, the test URL will need to be updated to work properly against the current test data.
These failures were also mentioned on #322 here.
The text was updated successfully, but these errors were encountered: