{"id":4758,"date":"2016-03-19T22:32:05","date_gmt":"2016-03-19T22:32:05","guid":{"rendered":"https:\/\/www.process.st\/templates\/software-testing-tutorial\/"},"modified":"2024-02-28T16:42:38","modified_gmt":"2024-02-28T16:42:38","slug":"software-testing-tutorial","status":"publish","type":"post","link":"https:\/\/www.process.st\/templates\/software-testing-tutorial\/","title":{"rendered":"Software Testing Tutorial"},"content":{"rendered":"
\n

Introduction <\/h2>\n
\n
\n <\/a>
\n <\/figure>\n<\/p><\/div>\n
\n

Nobody likes to doubt their own ability, especially when it comes to something as logic-driven as software engineering. In an ideal world, there would be no need for this software testing tutorial, and all programmers would sit safe in the knowledge that they wouldn't have to spend the next 18 months<\/a> revisiting the same code.<\/p>\n

Sadly, however, human error<\/a> is here to stay.<\/p>\n

To help you negate as much of this as possible, we here at Process Street<\/a> decided to rustle up our very own software testing tutorial! Use this bad boy to finely comb you individual sections of code before submitting them to your software deployment<\/a>.<\/p>\n

Just a heads-up before we begin, this tutorial only covers unit testing (testing the code to make sure that it works when standing alone).<\/p>\n

Let's get started!<\/p>\n<\/p><\/div>\n<\/section>\n

\n

Preparation: <\/h2>\n<\/section>\n
\n

Record the basic details <\/h2>\n
\n

First up in our software testing tutorial, you need to record the details of the procedure in order to fully document the process. Do so by filling in the form fields below.<\/p>\n<\/p><\/div>\n

\n
\n