-
-
Notifications
You must be signed in to change notification settings - Fork 644
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
Fix unit tests #631
Comments
I'm working on this, but the comments are failing. I don't know if comments are even available anymore, I don't remember where they are, or what they are for or are about. I'm not sure if we can still even get comments. Wondering if they can be disregarded now. |
Hey @tpwatson I'm not positive but I think the comments field used to include the inline review texts that were loaded on the main app page (as opposed to the full review list exposed by the So as an example, for this app it would be these reviews at the bottom: |
Example from an earlier version of the README: Line 75 in 84f5e93
|
Thanks for the clarification. I have all tests passing, all though randomly the throttle test fails due to a timeout error. I'm not sure if it's because we still need to get got updated. But the requests probably are not returning fast enough sometimes. |
are you already overriding the timeout threshold (as done here)? |
No I just left it as is. I thought I had them all passing but running into trouble with suggested search tests failing. Trying to figure out how to get the mappings working. 75 passing (1m)
ds:4 is correct in: |
So I've figured out how to count the mappings in an easier way, if I can actually fix the mapping issue I'll document it in the code for future use. But here is how to work with mappings and count them: Get a full copy of the AF_initDataCallback object, its not JSON but you can use a Javascript object to JSON converter: Paste the JS object in that site and you'll get the JSON version. Then copy the JSON version and take it to: Then you can find out the position of each piece of data much easier. But what I've gotten stumped on now, is that when you misspell a search term, like 'runing app' instead of 'running app' the mappings will be different from the correctly spelled results. So I have the mappings to correctly get the data for suggested search, but I'm trying to figure out how to put that into the search.js file so that when the results page has "Searching instead for [correct spelling search term]" it will use the other set of mappings. It's a lot to digest how the current codebase works, I'm struggling to figure it out 100%, especially because ramda is essentially a blackbox for me, but I'm trying. |
Closed by #649 |
In case someone has the time (I don't), it would be very helpful to get the unit tests back passing. This would simplify the PR review and merge process since it would make it obvious when code changes break things.
The text was updated successfully, but these errors were encountered: