You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What's scary isn't that the parser will crash when the NRS changes ... it's that it will simply produce incorrect output. That's exactly what is happening with bug #44. Many Title names are gobbledygook. But the program completed without an error message. And when I update the code to correctly parse the current format (by updating my fixtures from the live HTML), it will work, for a while. And then, the same thing may happen again.
What's interesting, though, is that the current out-of-sync code does fail tests when the fixtures are updating from the live website. Which gives me an idea: make the app self-testing. After downloading the latest HTML to export as JSON, it should first run its test suite on the new input files. Only if the tests pass should it continue to run the full application.
The text was updated successfully, but these errors were encountered:
What's scary isn't that the parser will crash when the NRS changes ... it's that it will simply produce incorrect output. That's exactly what is happening with bug #44. Many Title names are gobbledygook. But the program completed without an error message. And when I update the code to correctly parse the current format (by updating my fixtures from the live HTML), it will work, for a while. And then, the same thing may happen again.
What's interesting, though, is that the current out-of-sync code does fail tests when the fixtures are updating from the live website. Which gives me an idea: make the app self-testing. After downloading the latest HTML to export as JSON, it should first run its test suite on the new input files. Only if the tests pass should it continue to run the full application.
The text was updated successfully, but these errors were encountered: