Key Points In Web Applications That Should Be Focused On While Doing Manual Testing

Manual testing is a crucial step in the development process of any web application. 

It involves testing the application manually, as opposed to automated testing, to ensure that it works correctly and meets the requirements of the users.

Additional specific testing to be done for web applications.

There are several key points that should be focused on while performing manual testing on a web application, and in this article, we will discuss each of them in detail.

Points to Be Focused On During Web Application Testing 

Following points are to be considered for testing Web applications.

1. Functionality
2. Usability
3. Compatibility
4. Security
5. Performance
6. Error Handling
7. Accessibility

Let’s see them in detail.

I will be referring to Gmail application for example here.

Functionality Testing

Functionality is the first and most important point to focus on while performing manual testing on a web application.
This includes verifying that all the features of the web application are working as intended, and that there are no broken links or missing elements. 

Functionality testing is the combination of testing the application with Positive scenarios and Negative scenarios.

Based on the process in your organisation, Smoke testing, Regression testing and System testing are part of Functionality testing

For example, if the web application has a search feature, it should be tested to make sure that it returns the correct results when a user inputs a query.
Additionally, it’s important to test all the buttons and links to ensure that they are working as expected.

Will you continue using Gmail if it fails to send emails?

Typical Testing Scenarios For Functionality Testing:

1. Test that Gmail application can send mail to correct recipient
2. Test that new mail is received from sender in Gmail application

Is Software Testing Difficult ?

Usability Testing

Usability is another key point to focus on while performing manual testing on a web application.
This includes testing that the web application is easy to navigate and use, and that the user interface is intuitive and user-friendly.
This is important because a web application that is difficult to use will discourage users from using it, and will ultimately lead to a decrease in the number of users.
For example, a web application that has a confusing or cluttered interface will be difficult for users to use, and as a result, they will be less likely to use it.

Will you prefer to use Gmail if you struggle to find ‘Compose mail’ button?

Typical Testing Scenarios For Usability Testing:

1. Verify that user is able to easily compose the email in Gmail application
2. Verify that user can clearly differentiate read and unread emails in Gmail application

Compatibility Testing

Compatibility is also an important point to focus on while performing manual testing on a web application.
This includes verifying that the web application works as expected across different web browsers such as Chrome, Firefox, Edge, Safari etc and devices (like mobile, Laptop, desktop, iPad etc devices).
Note that this is important because a web application that does not work correctly on different devices will not be accessible to all users, and will ultimately lead to a decrease in the number of users.
For example, a web application that only works on Google Chrome will not be accessible to users who use other web browsers.

Will you use Gmail if it opens only laptop Chrome and not in mobile browser?

Typical Testing Scenarios For Compatibility Testing:

1. Test that Gmail application is working as expected in Chrome and Safari browsers
2. Test that Gmail application is completely displayed when opened in mobile browser

Security Testing

Security is crucial.
Makes sure that web application is secure and that it properly handles user input to prevent injection attacks and other security vulnerabilities, such as Cross Site Scripting (XSS).
This is important because a web application that is not secure can be vulnerable to hacking and data breaches, which can lead to sensitive information being compromised.

This will lead to cyber attacks, Ransomwares etc.
For example, a web application that does not properly validate user input can be vulnerable to SQL injection attacks, which can lead to sensitive information being compromised.

Do you think you will use Gmail if other users can see your emails?

Typical Testing Scenarios For Security Testing:

1. Test that Gmail application login has 2 Factor authentication
2. Test that one user of Gmail can not access other user’s Inbox

Performance Testing

Performance is also an important point to focus on while performing testing a web application.
This includes verifying that the web application is fast and responsive, and that it can handle a high number of concurrent users without crashing or freezing. 

Performance Testing includes Stress Testing & Volume Testing also.
This is important because a web application that is slow or unresponsive will discourage users from using it, and will ultimately lead to a decrease in the number of users.
For example, a web application that takes too long to load will be frustrating for users and they will be less likely to use it.

OK. Let me know if you still prefer to use Gmail if it opens after 20 seconds even with high speed internet connection?

Typical Testing Scenarios For Performance Testing:

1. Test that Gmail application loads within 2 seconds when opened in any browser
2. Test that Gmail application works as expected when 10 million users open it in a browser at a same time

Error Handling Testing

Error handling is also an important point to focus on while performing manual testing on a web application.
Error handling is important from the point of view of user experience.
This includes verifying that the web application properly handles errors and displays appropriate error messages.
This is crucial, because a web application that does not properly handle errors can be confusing for users, and can lead to them giving up on using the web application.
They might opt for other applications.
For example, a web application that does not display any error message when something goes wrong will be frustrating for users and they will be less likely to use it.

Imagine that you forget to enter To address and click on send button. Thing happens. No error message is displayed. Is it not frustrating for you?

Typical Testing Scenarios For Performance Testing:

1. Verify that you try to send an email in Gmail without To (recipient) address, proper error message is displayed
2. Test that error message is displayed when you try to send email without subject or mail body in Gmail

Accessibility Testing

Accessibility is another key point to focus on while performing manual testing on a web application.
This includes checking that the web application is accessible to users with disabilities and conforms to accessibility standards such as WCAG 2.1.
The application should have correct fonts, colour combinations etc.
The screen reader should read out the page contents out loud.
The web application under test should also be worked on, without using a mouse.

This is important because a web application that is not accessible to users with disabilities might lose those customers.

If your mouse or track pad is not working and you can only send mail through keyboard operations, do you think its is important for Gmail to have good accessibility ?

Typical Testing Scenarios For Accessibility Testing:

1. Verify that all the menus are properly displayed with good color contrast in Gmail
2. Verify that when perform tabbing, control moves to next menu in Gmail

Conclusion

While performing manual testing on web applications, it is important to focus on several key points to ensure the quality and functionality of the application.
These include the functionality of the user interface, the usability and accessibility of the application, the compatibility with various browsers and devices, the security of the application, and the performance and scalability of the application.
By paying attention to these key points, we can ensure that the web application is tested and meets the needs of users.