Sample Questions Best site for GRE, LSAT, SAT, GMAT, TOEFL, CCNA, CCSA and interview sample questions  

Web Testing Interview Questions

Web testing is the same as software testing that focuses on Web applications. It enables the complete testing of a Web based system before it goes live. This helps address system related issues before the system is open for public. Web testing interview questions include top 10 questions that you will come across when you appear for the Web tester's interview. You need to possess thorough knowledge of various fields of Web testing such as security of Web application, basic functionality of the site, its accessibility to the users, as well as readiness for predicted traffic and the number of users, and the ability to sustain massive spikes in user traffic.

Let us have a look at the list of some sample Web testing interview questions.

Question 1: What are typical problems that you come across in Web testing?

This question is relatively easy and meant to make you comfortable for the rest of the interview. This is a basic question and you must be able to answer it. While working as a Web tester, server problems are the most common that we come across. The server problem could be anything from server down or server under maintenance. Other problems next to server problems are hardware and database problems. These three are considered to be major issues while working in the Web testing field. Other similar problems that we often come across are functionality problems, UI related issues, security and related issues, operating system compatibility and browser compatibility problems, performance issues, and loading related problems.

Question 2: What types of Web testing security problems are there? What are the reasons?

Security and related problems are major in Web testing. The most common of them are Denial of Service (DoS) attack and buffer overflow. The most possible reasons for such problems are checking reactions for the invalid input options for login ID and password, pasting internal URL into the browser address bar directly without login, and viewing of other stats by the user.

Question 3: What are possible factors that influence the testing strategy of any website?

The factors that influence manual testing and automated testing are different from each other. Explain both the aspects in brief. Try to avoid long answer and thus, be clear and to the point. If the conditions are like unstable software, need for exploring new software, no automation suit available, test cases not planned, no any critical project, and only one time testing, then manual testing is recommended. However, when the conditions are like stable software, any applications associated with high risk factor, and need for repeated testing, then automated testing is recommended.

Question 4: What is the difference between testing in client-server applications and Web based applications?

This is one of the most commonly asked questions and considered to be the favorite question of the interviewers. Thus, be prepared for this one and answer confidently. In client server application testing, the test engineers conduct a variety of testings which are behavior testing (popularly known as GUI testing), error handling testing, back-end testing, and input domain testing. On the other hand, in case of Web based application testing, the testing engineers have to conduct a number of testings such as behavior testing, input domain testing, static Web testing, back-end testing, error handling testing, and frame level testing.

Question 5: What are the important scenarios for testing emails? How to test emails?

Testing an email seems an easy task, but it is not so. This scenario is a bit difficult technically. The protocol follows a long procedure and you must possess enough of practical experience so as to deal with the email testing issues. There are certain categories that you can divide your answer into and then explain the respective protocols. There can be four categories of testing emails:

for incoming email with an attachment or attachments, for outgoing email with and attachment or attachments, in case of email failure, and some other properties regarding edit, delete, and many more. After explaining these different scenarios, you can then describe the protocols for each one, if asked by the interviewer. This needs proper home work and practice on email testing.

  1. For incoming mail with attachment:

    1. Check the proper incoming address or ID
    2. Check Not only the One address (To), but also for the Cc and Bcc addresses
    3. Check the max and min limit for number of addresses
    4. Check if address has some error like @ or . is missing
    5. Check if address has more than 1 @ sign
    6. Check if . has arrived less than 1 time or more than standard time (as per registered)
    7. Check if address has arrived more than 1 time
    8. Check if address only have @, ., _ and special symbols that are standard signs
    9. Check that mail dose not have unnecessary content
    10. If there is or are any attachments then they open properly
    11. The attachment size has not exceeded the standard size
    12. If there are more than 1 attachment, then the calculated size must be under the Standard size
    13. If email content has some images or some different Flash pictures, it must be shown properly
    14. Sometimes email has some different extension files
    15. If the user reads the mail, then it should be marked as 'read'

  2. For outgoing mail with attachment:

    1. Check the Address as we done prior
    2. Here we must check for the attachments
    3. For all the send pictures
    4. Mail content should have the proper content

  3. Email failure:

    Check for the email failure problem and follow the protocol accordingly

Question 6: What would be your approach while starting to test a Web application?

This is a general question related to your typical work. Keep your answer brief and to the point here. Tell the interviewer that you would first go through the specification which is the primary interface to test any software. After going through the specification, your next job would be the GUI testing (behavior testing) and the functionality testing.

Question 7: How would you go for browser testing?

The events massaging and the GUI architecture are different for different browsers. Just like Firefox uses some GTK based massaging and IE uses Win32::OLE massaging. Thus, it is very difficult to generate a single standard script that can run on all the browsers; however, there are certain tools such as QTP and Winrunner that tend to use some complex protocols inside their architecture so as to handle various browsers. Hence, if your application does support different browsers such as IE, Fireforx, Netscape, and Opera, then you should be going for manual testing.

Question 8: What are some common website mistakes that cause configuration and compatibility bugs?

There are some common errors or mistakes that tend to create the compatibility and configuration bugs:

  1. Clicking on the links that show some fatal error
  2. Accepting invalid codes
  3. Accepting HTML codes
  4. Improper alignment
  5. Failing to submit the orders
  6. Popping up of forward and back navigation errors
  7. Improper location f the scalability changing Alignment (if it is not in the middle)

Question 9: Enlist the possible configurations that affect the testing strategy of a Website.

Various configurations that affect the testing strategy of any Website are browser software and version, browser plug-ins, browser setting options, hardware platform (PC or Mac), text size, video resolution, and color depth. Elaborate on each of the factor in brief, if asked by the interviewer and time permits.

Question 10: Explain white box testing and blackbox testing.

Both of these are software testing methods. White box testing is a method in which the internal structure, design, and implementation or function of an item is known to the tester. It is generally applicable for lower levels of testing such as unit testing and integration testing. Blackbox testing deals with the testing of internal structure, design, and implementation or function of an item which is not known to the tester. It is mainly applicable for higher levels of testing such as system testing and acceptance testing. White box testing is done by software developers; while blackbox testing is done by software testers.

The above mentioned questions are generally included in a typical Web testing interview questions list. Since they are provided along with their best suitable answers in the guideline, it might be useful for you to know what to expect by the interviewer. All the best!

Sample Test Questions
GRE Sample Questions
CAT Sample Questions
GMAT Sample Questions
TOEFL Sample Questions
ACT Sample Questions
SAT Sample Questions
LSAT Sample Questions
PSAT Sample Questions
MCAT Sample Questions
PMP Sample Questions
GED Sample Questions
ECDL Sample Questions
DMV Sample Questions
CCNA Sample Questions
MCSE Sample Questions
Network+ Sample Questions
A+ Sample Questions
Technical Sample Questions
WASL Sample Questions
CISA Sample Questions

Other Sample Questions
Sample Interview Questions
Sample Teacher Interview Questions
Sample Citizenship Questions
Accuplacer Sample Questions
Science Bowl sample Questions
Driving Test Sample Questions
Sample Survey Questions Sample Essay Questions
Sample Behavioral Interview Questions

Copyright © 2004-2013, Best BSQ. All Rights Reserved.