• info@helpingtesters.com
  • helpingtesters

SUBSCRIBE TO OUR NEWSLATER





Checklist for different Software Testing Types

February 7, 2018
Checklist for software testing, checklist for software testing types, software testing checklist, basic checklist for software testing, testing checklist

Software testing professionals are considered as the GUARD of the SDLC process. This is not because of their capability to finding and reporting bugs, but rather for delivering a high-quality product. It is the tester or QA who is responsible for the delivery of the qualified product.  And in order to do this, they generally follow a Checklist during the whole testing life cycle. So, the very next thing which comes in our mind is, What is the Checklist all about? And how it helps in improving the product quality? Does Software Testing Checklist imply for all the different testing types? What should be included in Software Testing Checklist for various testing types?

The word Checklist signifies a list of task that is being noted down or recorded for tracking purpose. It can be a haphazard list not arranged in proper sequences.           

In our daily day to day life, we also have a checklist to follow. Suppose on weekends we generally make a list of thing to be done like-

  • Wake up early and go for morning walk and reached home by 8 am.
  • Need to go to the bank by 10 am.
  • Go for lunch at 1 pm.
  • Go for a movie show in the evening.
  • Need to meet a friend after the movie. etc.

And once a task is done or over, we strike it off or tick it. This is the checklist we generally follow.

Now, When coming to testing, Checklist have many advantages in improving the software quality. Few of the advantages of using the Software Testing Checklist are:

  • The Software Testing Checklist can be easily created, modified and maintained.
  • Use of checklist helps in avoiding checking of the repetitive task and helps in the utilization of brain power in creative activities.
  • The checklist helps to stay in the more organized way and thus prevent skipping of any steps in the testing process.
  • Software Testing Checklist is very flexible and items can be easily added or removed from it.
  • With the help of a checklist, we can perform the repetitive tasks more quickly and effectively and with fewer mistakes.
  • The Software Testing Checklist provides a well-structured base for testing.
  • Checklist works a reminder for testers. Testers can recall the important test based on the checked items on the checklist.
  • The checklist helps in identifying and selecting the different tools required for different types of testing like performance testing, automation testing, etc.
  • Creating the entry and exit criteria required testing.

General Software Testing Checklist – Web and Mobile Applications

While performing the testing of the website or mobile application, the below mentioned general checklist for software testing has to be followed for, different testing types, improving the product quality. The Software Testing Checklist for different testing types includes:

  1. UI/UX Testing

            UI/UX testing is the testing where the implemented GUI is being tested by comparing with the project mock-up and UI design. It’s the UI of the application, which attracts the user. The more eye-catching the application GUI, the number of users. So, UI testing needs to be done with foremost importance.

UI testing is a type of non-functional testing. UI testing helps in identifying UI defects. The checklist to be followed while performing UI testing are :

  • Responsiveness- For the website, the web pages should be responsive and should fit in all mobile screens irrespective of the screen size.
  • Alignment- All the button, textbox, and other elements should be properly aligned and should look good.
  • Scrolling- The scroll in the page should work properly and there should be no horizontal scroll (unless required). The table can be displayed on the webpage with a horizontal scroll.
  • Spelling and grammar- All the text for label, content, error message, pop message, etc must be of correct spelling and grammar.
  • The logo should display properly and click on the logo should redirect to the homepage.
  • Image- Images are displaying properly throughout the web pages. There should be no distorted or broken image.
  • Page title with fab icon- For Website, every page should have a page title and should have the fab icon.
  • Look and feel- The color combination should be good and eye-catching. All the windows have proper look and feel that expresses transition.
  • Checking the behavior of the different controls like- checkbox, dropdown list, radio buttons, etc.
  • All the button and textbox should be consistent throughout the application.
  • Navigation- Check navigation for all menu and menu items. The navigation should be properly done for both keyboard and mouse.
  1. Functional Testing

Functional testing is the process where the feature is tested by comparing the overall behavior of the application with the specification. While performing the functional testing, the functional test case to be followed. Functional testing follows the concept of Black Box testing, where the internal logic of the application is not known to the tester.

The checklist for functional testing includes different types of testing, which are listed below:

  • Validation testing- It includes the validation of the different fields used in the application like- combo box, textbox, radio button, dropdown list, checkbox, etc.
  • Link Testing- Validating whether all the internal and external links are working properly as required. There should be no broken or dead links.
  • Email link validation- Checking whether the default email client should open with the email populating in the TO section when the user clicks on the email link.
  • Regression testing- It is a type of functional testing, which is done to identify that the existing feature is not affected by the recent or current code change.
  • Sanity testing- Sanity testing is a subset of regression testing, which is performed when there is lack of time. In sanity testing, it is tested that all the menus, functions, commands available in the project are working fine.
  • Smoke testing- Smoke testing is nothing but a build validation testing, where the main functionality of the application is tested. Thus ensuring that the build is stable enough for further testing.
  • Field validation- All the required field and the field validation is being properly tested.
  • Error message- Checking that the error message displaying for the field is proper and is a valid one.
  • Page or Form submission- Checking that the forms submission should work properly. And proper error message should display if any error is faced.
  • Tool identification- Identifying the tool required for performing testing. For example- If performing automation, then selecting the proper automation tool and framework required for the automation.
  1. Compatibility Testing

Compatibility Testing is a type of non-functional testing, which is generally performed to check the compatibility of the developer software/product or website/application under different environment. Compatibility testing is one of the important test types when performing Quality Assurance on a software development project. It is done against the different object like- Hardware, Browsers, Operating Systems, Databases, Devices and so on.

The checklist to be followed while performing compatibility testing are :

  • Hardware- It checks the software compatibility with different types of hardware devices like USB port, printers, etc.
  • Software- It checks the build software to be compatible with other software. For example- MS Excel should be compatible with MS Word, Outlook, etc.
  • Mobile- Checking the build software/application is compatible with mobile devices with different OS and with different sizes.
  • Operating System- It checks the compatibility of the software to run properly in different operating systems like Windows, OSX, etc.
  • Browser- Checking whether the built website is compatible and works properly different browsers.
  • Network- It checks the software compatibility in different networks with all parameters like Bandwidth, Operating speed, capacity, etc.
  1. Performance Testing

Performance testing is a testing practice that determines the system behavior under the certain workload. It also helps in measuring, investigating and validation different attributes of the systems like responsiveness, scalability, reliability, and resources used. Performance testing is categorized into different types like load testing, stress testing, scalability testing, etc.

The basic checklist to be followed while performing performance testing are mentioned below:

  • Performance testing isn’t for the completed project, it adds more value when testing individual unit or modules.
  • Need to get rid of the bottleneck and find out the amount of load/stress the site is able to sustain.
  • To check the performance, reliability, stability, and scalability of an application under the different workload.
  • For a web-based application, proper credential like URI should be provided for performance testing.
  • Tracking the response time with respect to the amount of task at a given point in time, the time taken by the application give back the results.
  • The test environment should be planned in advance and it should reflect the architecture as it is in production. The production and test environment should be equivalent in nature.
  • Load injectors are required for producing the required load in the application, which should be planned by the tester in advance.
  1. Usability Testing

Usability testing is an approach, where the product is tested from the users perspective. It is the type of Black box testing techniques. Usability testing focus on, How easy is it for the users to use the product. The general checklist to be followed while performing the usability testing are :

  • Registration – Unwanted registration should be avoided and if required there should be a proper registration form, which user can find and do the registration easily.
  • Relevant images and video- The images and videos displaying in the application should be relevant and should match the page content or with the app.
  • Company contact- The address and location can be easily accessible by the users.
  • The application is credible- Credible references, contact information, location, credentials, and images of real people are displaying in the application.
  • Content should be clearly visible and readable.
  • Links, button, checkbox and radio buttons should be clickable.
  • Links should be highlighted and there should be no broken or dead links.
  • There should be a site description in the window title.
  • Search button should be available on all pages and work properly.
  • Consistency- Page layout should be consistent in throughout the application.
  • The site should be responsive as per the screen size.
  • Custom Error page- There should be custom error pages for 404 and 500 error.
  • Forms should not be too long and only necessary fields should only be included.
  • Browser and device compatibility- The application should be compatible with all browser and devices as required.
  1. Database Testing

The database is one of the inevitable parts of the application. Database testing involves retrieving of values from the database by the application. It includes data integrity testing, data validity and testing of functions, triggers and procedure in the database. In Database testing, tester to expertise in checking tables, writing queries and procedures. The checklist to be followed for Database testing are :

  • Check the database name, table, columns, etc should match with the project requirement of the specification.
  • Verify the data encryption.
  • Try entering invalid data in the database.
  • Check all the columns should have a proper data type.
  • Validate the database behavior in case of any service failure.
  • Verify the connection of the application with the database.
  • Validate the restore and backup plan.
  • All the tables created should have a logical structure i:e; primary, foreign key, etc.
  • Validate the procedures should get triggered properly when required.
  • Procedure names should be properly validated.
  • The database is not supposed to receive “Null” value for any fields.
  • Check by inserting date and time in the invalid format.
  • Try inserting values which exceed the data boundaries.
  • Entered data should get successfully into the databases once the user clicks on Apply or Submit button.
  • To check whether the correct transaction is executed or not.
  • To verify and validate the normalization of the database.
  • Should also focus on the time taken in retrieving and updating the data.
  1. Security Testing

Security testing is a type of testing, which focus on finding the flaws in the security mechanism of an application for protecting data and maintain function as required. It focuses on finding all the possible loopholes and thus preventing data loss. The checklist which is to be followed by security testing are listed below:

  • Verify that password rule is implemented in pages like- Registration, Login and Change password page.
  • During registration, there should be captcha so that spam bots cannot register.
  • Once the password is changed, the user should not be able to get logged in with the old password.
  • There should be server-side validation for the mandatory fields.
  • Verify that important information like Password, Credit card information are in encrypted format.
  • Verify that anonymous user should not be able to access other user details by changing the page URL.
  • View Source code should be disabled and should not visible to users.
  • Check the SQL injection attacks in all pages of the application.
  • All cookies information should be stored in encrypted format.
  • Security answers should be stored in the database as hashes and not in plain text.
  • Verify user get blocked for 24 hours or more if tried to get logged in with invalid credentials for n number of times.
  • Cookies should not store the password.

Conclusion

To follow Software Testing Checklist during the process is a vital thing which should be incorporated in the testing phase and should be strictly followed by all testers. It not only helps the testers finding flaws or loopholes in the application but all help in improving the product quality to much extent. Project-specific Software Testing Checklist can be followed to make sure that all the required verification points are tested

When the new project is about to start, it is wise to start writing the Software Testing Checklist and keep it updated as and when the requirements changes / gets added/deleted. 

Ram Prakash has worked in various domains of testing including security, performance, security testing and automation testing. Including several tools like QTP, selenium, LoadRunner,JMeter, VSTS Coded UI, soap UI, Burp Suite etc.

About the author

RamPrakash Singh author

Ram Prakash has worked in various domains of testing including security, performance, security testing and automation testing. Including several tools like QTP, selenium, LoadRunner,JMeter, VSTS Coded UI, soap UI, Burp Suite etc.

Leave a Reply

Your email address will not be published.