Curriculum: Refactor our Node "Adding Backend Testing" topic outline

[alodahl]

Curriculum feedback:

• “It was hard to understand Adding Backend Testing to your projects. It was a long text and objectives were not clear.”
• “The lesson 'Adding Backend Testing to your projects' wasn’t really clear, it was a long text, objectives were not clear, there were a bunch of typos, too many links for reference that end up not helping, too difficult to follow.”

Task:
The first step of our backend section re-vamp was addressed in this issue with this new outline. Use this outline as a launching point as you help us replace the Adding Backend Testing outline with new bite-sized, focused outlines. Help us decide what the next outline should be, and put it in our /backend folder.

Please note:

• The best use of apprentice's time is when they can add value directly to one of their existing projects. Look at any API they may have built after starting the Server-side Development && Agile Programming, but before Assessment #8. If you are going to rewrite anything, have them build tests that strengthen an existing project of theirs.
• This lesson will be in the roadmap before the apprentices learn APIs, Express, SQL, and other backend concepts. It should give an overview of what backend development is, giving a good foundation for the apprentices to understand future lessons.

Some possible resources to include:

https://learntocodewith.me/posts/backend-development/
https://simpleprogrammer.com/what-is-back-end-development/
https://www.coursereport.com/blog/front-end-development-vs-back-end-development-where-to-start

Direct questions to @alodahl and/or @vegetabill , and keep them informed of your decisions and progress as you go. Once you are done, create a PR with your changes.

For FAQs on how to contribute, see: https://github.com/Techtonica/curriculum/blob/main/CONTRIBUTING.md

[Nikhil-Vats]

Hey, I want to work on this. Already signed up. Should I just fork, work on it and send a PR when it's done?

Also, I read that there's a slack group for communication but I couldn't find a link so that I can join it.

[alodahl]

Hooray, thanks Nikhil! If you filled out the volunteer form, you should get an invitation to the slack channel in a week or so. In the meantime, feel free to ask questions here.

[Nikhil-Vats]

I have changed the objectives and the outline by dividing the lesson into distinct sections to make it more understandable. There's still a lot left to do.

1. I will improve the Guided Practice section a little bit to make it more understandable.
2. Remove unnecessary links.
3. Fix typos and make the language a bit easier wherever it goes too technical.
4. Any other improvements you suggest.

I am also planning to add a short example to summarise the use of Postman.

[Nikhil-Vats]

Hey, I think the following links in Specific things to teach can be moved to Supplementary materials -

• Simple Mock
• Nock (intro tutorial)
• Supertest (intro tutorial)

[alodahl]

Those links aren't used in the body of the lesson? If not, then you can move them to supplemental materials with a short description of why they're useful.

Thank you so much for tackling this one!

[Nikhil-Vats]

@alodahl Thanks for merging my previous commit. I am vacationing so it is taking a bit more time to do this. Will update the PR soon!

[Kundan28]

@vegetabill @alodahl Could this be worked under GSSoC20 ?

[vegetabill]

No

[Kundan28]

Okay.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[alodahl]

Hey, I think the following links in Specific things to teach can be moved to Supplementary materials -

• Simple Mock
• Nock (intro tutorial)
• Supertest (intro tutorial)

@vegetabill could we change the ACs to completing these tasks? I don't want the issue to be automatically closed just because it has been neglected.

[vegetabill]

I will review and split this up

[vegetabill]

We no longer need this. Superseded by #1216