QA Software Testing Interview Questions for Beginners and
Experienced Candidates:
Q 1) What is the Process for Creating a Test Script?
Step 1: is to get a thorough understanding of the AUT:
This could be by reading the requirement documents
thoroughly.
We can try to understand any point of reference that
we have – a previous version of the application or wire-frames or screenshots
Step 2: After understanding the requirements, we make a list of what are
the areas in this application that will have to be tested. In other words, we
identify the test requirements. The focus in this step is to identify “What” to
test. The outcome of this step is a list of Test Scenarios.
Step 3: Once we have the test scenarios, we concentrate next on “How” to
test them. This phase involves writing detailed steps about how to test a
particular feature, what data to enter and what is the expected result.
Once these 3 steps are done, we are ready for testing.
Q 2) what are the fields in a Bug Report?
Answer: Following important
fields should be included in a good Bug Report:
Defect Description: a short describing what the bug
is.
Steps to Reproduce: details about how to arrive at the
error, exact test data, the time at which defect was found(if applicable)
environment: any information that will help re-encounter the issue
Module/section of the application (if applicable)
Severity
Screenshot
Q 3) How to test a customer-facing software?
Answer: With any application that we test, we are trying to
see if a certain set of requirements are met by the application or not. But
when it comes to a user-facing site, apart from concentrating on functionality,
we also have to look into a few usability features, maybe performance and
security aspects also to a certain extent.
The first level of testing is: Does the site satisfy
its functional requirements.
The next level of testing is: how easy is it to use
the site, do the options make a logical sense and meet the expectations of the
user or not.
For Example, if the user has to be pass 3-4 screens to
submit the basic information they are going to be annoyed, so such issues have
to be addressed.
Performance Testing to the complete extent might not
be in scope but simple situations like, how long does the search results take
to be displayed and how much time does it take for the system to retrieve a
customer info at the peak hour – these are some example of the kind of things
we would want to keep an eye on.
Security – for sites where there is a secure login to
access the site, the minimum functionality around it has to be tested. For
Example, if I leave the site idle for more than 10 minutes, is it auto logging out
or not. Something as basic as that should be focused on.
Q 4) How to overcome the challenge of not having input
documentation for testing?
Answer: IF the detailed standard documentation like BRD and FSD are
unavailable, the tester will have to depend on some point of reference.
A previous version of the application
Another factor that helps immensely, is to talk to the
developers or the business analysts (when available) to get a confirmation on
our understanding or clarifications in case of doubts.
When none of these situations works, we can just
conceptualize the application based on our previous IT application experience
and create the basic set of test scripts. When the testing phase comes up, we
can set up a portion of test cycle time and do some test case management (make
the already created scripts perfect) so we have the doc for the next phases.
Answer: The onsite coordinator is a point of contact for the offshore
team and to the client for any information regarding the testing.
KT from and to offshore and clients
Getting the environment to test all ready
Sanity testing, smoke testing
Testing – the key functionality.
Bug review – found by the offshore team
Bug assigning to the respective dev
Presenting metrics
Providing sign off
Yes, even an onsite coordinator has to test.
Answer: Every bug has to be noted and analyzed – whether it is
encountered at onsite or offshore, whether repeatable or not. A real value-add
to a tester’s job is when we involve ourselves in the Root Cause Analysis
process for a bug rather than simply reporting it.
All the onsite and offshore team members should follow
a guideline that screenshots had to be taken for every error that we encounter
– repeatable or not.
If there are logs, system files or anything like that,
that might help us find any evidence of the issue- we should try to find it.
Despite all these steps, if we still can’t tell why
and when the problem occurs- we should report it to the developer all the same
– with as much information as we can.
Q 7)
Video/audio related testing – What does this include?
Answer: How to test an application having video or audio?
Here are the important points to consider:
Access levels (restricted or not – password
controlled)
Different kinds of environments
Browser compatibility
Screen resolutions
Internet connection speeds
The specific options on a video – like play, stop,
mute, etc.
Video by size
Response to the videos – comments (limitations on the
comment length and number of comments it can take)
Video responses to the videos
Interface with social networking sites –
Interoperability
Buffering speed
Embedding the video
Q 8) Mobile Application Testing – What does it include briefly?
Answer: Mobile App Testing Important Test Scenarios:
Usability of the features on a mobile screen.
Testing it on different mobile platforms – like
Android and iOS.
Installations, uninstalling, launching the app with network
and without a network, testing functionality.
Network connections –WiFi, 2G, etc.
Logs at iOS iPhone configuration utility for Android
Monitor.bat can be used for debugging.
No comments:
Post a Comment