As you may have heard, @em-ant, @Greenheart, and @systimotic have been hard at work building projects with testable user stories. We are looking for a few volunteers to attempt to build these based on their automated tests.
The goal is for campers to be able to build these projects step by step following user stories. This will make the projects less intimidating and more fun. Oh, and donāt worry - weāll still have plenty of optional projects where we donāt provide you with any tests. And if youāve previously built these projects, you donāt need to build them again.
If youāre interested in attempting this, please reply to the thread and let us know youāve started it. The more people who want to build this, the better, as we can start gathering feedback.
@Em-Ant The only thing I noticed about testing my project is that I had to include the protocol in the input#url textbox to get the tests to pass. Any URL that did not include the protocol was treated as a relative URL.
zackward.net/projects/request-header-parser Doesnāt work www.zackward.net/projects/request-header-parser Doesnāt work https://www.zackward.net/projects/request-header-parser Works
Are you talking about the āTesting frameworkā right ? Iāll try to fix it, but it is just a temporary tool. We are developing a dedicated view in the FCC site that will hold the testing functionalities. Thanks for you feedback
Did this a few months back, the only things I had to change were to add cors and use the entire language and software fields (i.e. "language":"en-US,en;q=0.8" rather than "language":"en-US" which is what the old output was supposed to be like).
Other than that it was a painless conversion, and all the tests pass now.