-
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
[Bug Report] - Fix Failing Tests #662
Comments
I've written a few of the tests now but would appreciate some assistance so we can get this done sooner rather than later. I'm not the quickest at these. |
I'm fairly sure a bunch of these are timeouts which can be fixed by bumping up the global test timeout time or on a per-test basis. |
@andycwilliams I may have accidentally fixed them all on #666, take a look. |
@andycwilliams I don't see any obvious problems with BasicInfo or HousingInfo so I checked them off. Please let me know if there are others you'd like picked up (Profile?). |
Added my name next to Profile. |
Several more tests have been written as of #667. Only a handful more to go. |
@AJSterner Any news on tests for Profile? I'm aiming to get MVP wrapped up soon as possible. |
@andycwilliams Profile tests ready for an initial review: |
Closed out Profile tests! |
Work on this can begin right away. However, it should not be submitted until ensuring there are no additional failing tests from #571 and #606.
Component tests to fix:
Describe the bug:
Some of the tests are now failing.
Expected behavior:
Every test should pass to ensure maximum test coverage possible.
To Reproduce:
Steps to reproduce the behavior:
npm run test
in the terminalAdditional context:
The tests fail due to changes in the related components. So they should be updated or, when relevant, rewritten according to each component's new specifications. For example, some have been broken up into multiple smaller components and so will need additional tests.
CivicProfile
andFinancialInfo
are not yet implemented and therefore do not require tests at this timeThe text was updated successfully, but these errors were encountered: