What is manual testing? — Pragmatic Software Testing
Manual testing of software is the exercise of following sets of steps as an end-user by the tester to validate the completeness of said functionalities. In other words, the tester would try to find out the missing or malfunctioning functionalities.
There can be many types of manual testing that can be undertaken by the testers. The most common type of testing is Acceptance testing.
We will do a real-world example now.
Test Scenario 1: Book Free Consultation Test.
You will create a test story with the following steps in any scrum software or even in an excel sheet. I always use Atlassian Jira for all my freelancing projects.
Step 1: Go to the website’s page, https://fireantnetworks.co.uk
Step 2: Click on the Book Free Consultation button.
Step 3: Pick the future Date Time from the Calendar
Step 4: Click on the Time populated on the right hand of the calendar and confirm.
Step 5: Input the following fields, First Name, Last Name, email, Add Guests, Phone number, and any other details in the share text description field.
Step 6: Accept the cookies too. if any
Step 7: Click on the Schedule Event button.
Step 8: You should receive an email with the selected details.
Step 1: Go to the website’s page, https://fireantnetworks.co.uk
Step 2: Click on the Book Free Consultation button.
Step 3: Step 3: Pick the future Date Time from the Calendar.
Step 4: Click on the Time populated on the right hand of the calendar and confirm.
Step 5: Input the following fields, First Name, Last Name, email, Add Guests, Phone number, and any other details in the share text description field. Validate each field type as per field type.
Step 6: Accept the cookies too. if any
Step 7: Click on the Schedule Event button.
Step 8: You should receive an email with the selected details.
Potential Results of Test Scenarios 1
1. Test Passed: Every Step worked as expected including the validation of fields’ values and email received with the confirmation of emails with correct format and details about the meeting.
2. Test failed: If there is anything that did not work as expected or defined by the BA in the story.
For example, You did not receive the email or email arrived with incorrect details or any typo mistakes in the email or even you were not able to click the book button, etc. or Even if Confirm button took a while which might be a potential performance issue with the form.
Note: You are supposed to inform the development team of the bug by commenting on the JIRA story or email them including CC scrum master. For example,
