Software Testing Practical Training
                      
iFour Consultancy
Software Testing Training
 
Practical Training
https://www.ifourtechnolab.com/aspdotnet-web-development
Practical Training
⚫Functional Testing
⚫Verification and Validation
⚫Regression Testing overview
⚫Cookie Testing fundamentals
⚫Session Testing fundamentals
⚫API Testing
https://www.ifourtechnolab.com/aspdotnet-web-development
Functional Testing
Examples of Functional testing are
Identify Test data
• Unit Testing
Check expected outcome with selected input data • Smoke Testing
• Sanity Testing
•
Execute test-cases Integration Testing
• White box testing
• Black Box testing
Compare Expected and Actual result • User Acceptance testing
• Regression Testing
https://www.ifourtechnolab.com/aspdotnet-web-development
Verification and Validation
Requirement 
System Testing
Analysis
High-level Integration 
Design Testing
Low-level Design Unit Testing
https://www.ifourtechnolab.com/aspdotnet-web-development
Coding Coding
Regression Testing Overview
Some regression testing examples are here.
⚫ When new functionalities are added to the application.
Example: A website has a login functionality which allows users to do login only with Email. Now the new features look 
like “providing a new feature to do login using Facebook”.
⚫ When there is a Defect Fix.
Example: Imagine Login button is not working in a login page and a tester reports a bug stating that the login button is 
broken. Once the bug is fixed by the developers, testers test it to make sure whether the Login button is working as per 
the expected result.  Simultaneously testers test other functionalities which are related to login button
⚫ When there is a Performance Issue Fix.
Example: Loading the home page takes 5 seconds. Reducing the load time to 2 seconds
� Note: We do regression testing after every deployment, so it would make life easy to automate test cases instead of running 
manually on each and every time. if we have thousands of test cases, it’s better to create automation test scripts for the test 
cases which we do on every build
https://www.ifourtechnolab.com/aspdotnet-web-development
Cookie Testing Fundamentals
⚫A cookie is a small piece of information that is stored in a text file on user's (client) 
hard drive by the web server. 
⚫That information is then sent back to the server each time the browser requests a 
page from the server.
⚫Usually, cookie contains personalized user data or information that is used to 
communicate between different web pages.
⚫Session Cookies: These cookies are active till the browser that triggers the cookie is 
open. When we close the browser this session cookie gets deleted
⚫Persistent Cookies: These cookies are written permanently on the user machine 
and it lasts for months or years
https://www.ifourtechnolab.com/aspdotnet-web-development
Cookie Testing Fundamentals
How to test Cookies – Sample Test Cases
⚫Disabling cookies: Disable all cookies and attempt to use the site's major functions
⚫Corrupting cookies: Manually edit the cookie in notepad and change the parameters with 
some random values
⚫Cookies encryption: Sensitive information like passwords and usernames should be 
encrypted before it is sent to our computer
⚫Cookie testing with multiple browsers: Check your website page is writing the cookies 
properly on a different browser as expected
⚫Access to cookies: Cookies written by one website should not be accessible by others
https://www.ifourtechnolab.com/aspdotnet-web-development
Session Testing Fundamentals
⚫Sessions are server-side files which contain user information
⚫A session ends when a user closes his browser
⚫For Cross-Session testing, 
⚫Open web-application console and check session details of 1st user.
⚫Now export in notepad and import it in 2nd user.
⚫Now check webapp behavior and role management functionality
https://www.ifourtechnolab.com/aspdotnet-web-development
API Testing
Example
⚫Request for weather on our mobile phone we are basically doing all these using API.
⚫So whenever we request for weather we actually sends a request to the server request is 
nothing but a predefined form of data sent to the server in a defined format.
⚫Now, when this data is received by the server it reads it and send the response accordingly 
if the request sent is valid one
⚫So, I guess one of the parameter in the request body might be city name or Pin Code of 
the city, so for the purpose if testing it we might send different cities, blank city or some 
invalid city name and we can see what kind of response we receive.
⚫For validation purpose, if we are receiving the few specified details for that particular city, 
also in most of the cases we also check for response codes.
https://www.ifourtechnolab.com/aspdotnet-web-development
API Testing
Few helpful response codes
Response Code Meaning
200 Ok
202 Accepted
301 Moved Permanently 
307 Temporary Redirect
400 Bad Request
401 Unauthorized
403 Forbidden
404 Not Found
408 Request Timeout
500 Internal Server Error
502 Bad Gateway
503 Service Unavailable
504 Gateway Timeout
https://www.ifourtechnolab.com/aspdotnet-web-development
Thank you..
https://www.ifourtechnolab.com/aspdotnet-web-development