Request Header Microservice with testable user stories - Guinea Pigs needed 🐹 News

Request Header Microservice with testable user stories - Guinea Pigs needed 🐹 News
0

#1

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.

Thanks, and happy coding!

The project tester (enter the public HyperDev URL for your project and set it to MS_2 header parser): https://narrow-plane.hyperdev.space/

Working example: https://hyperdev.com/#!/project/dandelion-roar

Boilerplate : https://hyperdev.com/#!/project/shard-weed


#2

Live version: https://cagey-beef.hyperdev.space
Code: https://hyperdev.com/#!/project/cagey-beef

I got a bit confused about 1st test - it says 1.get a valid ip(v4), but expects something that looks like IPv6. Am I missing something?


#3

Sorry I forgot to update the test description. It’s fixed now.
Any other feedback ? Can we improve something ?
Thanks. :slight_smile: :thumbsup:


#4

I built this today and discovered that the tests will work even though my project is deployed on my VPS! Very nice! :smile:

Live version: Request Header Microservice
GitHub repository: https://github.com/ZackWard/request-header-parser


#5

@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


#6

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 :smile: :thumbsup:


#7

Awesome! Great work. Thank you for helping QA all of these projects. This is extremely helpful for us.


#8

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.

Code : https://gomix.com/#!/project/bloom-wolverine