Web Testing Interview Questions
In this section we discuss some common Web Testing Interview Questions and Answers.
These questions are specific to web testing.
Q: How is Web Application Testing different to Desktop Application Testing?
A: Web Applications are typically hosted on a server which we can access via a web browser, where as desktop applications are installed on the client’s machine.
This setup opens a whole new testing challenges: Performance and Security testing become important as the application is open to a wide audience. Good design and usability are also important.
Other important factors that come to play are testing on multiple browsers, multiple devices, redirection and responsiveness.
Q: What are the HTTP response code blocks and what do they mean?
A: After a request is sent to a server, there are different possible response codes which can be returned by the server:
The blocks are:
- 2xx for Success, the most common one is 200 which means “OK”.
- 3xx for Redirection, the most common ones are 301 and 303 which mean “Permanent Redirect” and “Redirect for Undefined Reason”, respectively.
- 4xx for Application Error, the most common ones are 403 and 404 which mean “Forbidden” and “Not Found”, respectively.
- 5xx for Server Error, the most common one is 500 which means “Server Error”.
Q: How would you Test a Service Oriented Architecture (SOA) Web Application?
A: The testing of web applications that communicate with a web service can be broken down in two parts:
- Testing of the Web Service in isolation. Each web service has one or more functions which can be tested by sending appropriate requests and analyzing the response and verifying correct data is returned in the response. We can use tools such as SoapUI to test a Soap Service or Rest Client to test a RESTful web service.
- Integration Testing of Web Service with the Front End. The integration testing is also important as it can highlight issues with data in the request and display of the response.
The reason for this separation is to be able to identify issues in the web service much quicker and easier to debug.
Q: Suppose you have a Login form which is connected to an Authentication Web Service. What tests would you perform at which layer?
- All the input/output validation should be tested at the API layer calling the Authentication Web Service. Tests such as valid/invalid username/password combinations as well as verifying correct error messages.
Q: There are many ways to test a website and there could be lots of test cases to execute, how can you make sure the we b application is fit for release?
- We can Automate majority of test cases, but most importantly we can use test techniques such as Pair-wise testing to reduce combinations and/or model based testing to plan user journeys to ensure major functionality of web application works.
- We can also use analytics to gain insight into what users do on the website, which page is most popular and which feature is most used by users.