Qa Interview Questions
Qa Interview Questions
Types Of Defects:
➢ Bug in Code
➢ Bug in Design
➢ Bug in Requirement
What is VERIFICATION?
Checking that we are building the system right.
What is VALIDATION?
Checking that we are building the right system.
What is FAILURE?
❏ Some functionality of the application is not working.
SEVERITY:
★ Severity of a defect means how much impact the defect has on the
business of the application.
★ Severity of a defect can be
○ BLOCKER
○ CRITICAL
○ MAJOR
○ MINOR
★ BLOCKER:If any defect has stopped the further testing activity.
★ CRITICAL:If any defect has a high impact on the business of the
application.
★ MAJOR:If any defect has moderate impact on the business of the
application.
★ MINOR:If any defect has low impact on the business of the
application.
PRIORITY:
❏ How fast the defect has to be fixed.
❏ Generally priority can be High, Medium and Low.
RISK:
Risk is a problem which has not happened yet and it may not happen in
future also.
What is Debugging?
❖ Debugging is the process of fixing a bug in the software.
❖ It can defined as the identifying, analyzing and removing errors
❖ Testing is the process to find bugs and errors
❖ Debugging is the process to correct the bugs found during testing.It
is the process to identify the failure of implemented code.
What is an EPIC?
★ Requirement Collection:
○ In this phase the requirement is collected from the customer by a
Business Analyst service based company or product based
company in the form of CRS(Customer requirement specification) or
BRS(Business Requirement specification) .And the Business Analyst
covert CRS into SRS(Software Requirement Specification).
★ Feasibility Study:
○ Technical Feasibility:
■ In this software architect and senior developer will decide if
technology is available to finish the project and if it is available
then which technology is required.
○ Resource Feasibility:
■ Human Resource decides how many people are required to
hire from the outside.
○ Financial Feasibility:
■ In this financial department will calculate the cost for the
technology and cost for the resources based on technical and
resource feasibility.
■ If there is any profit, the finance department will check whether
the profit generated is substancial or not.If it is substantial
then the project will be approved otherwise it will be rejected.
★ Design:
○ High Level Design(HLD):
■ Software Architect and senior developer will decide how many
modules should be in the application and then how each and
every one of them will be connected with each other and their
connections with database and network servers.
○ Low Level Design(LLD):
■ In this Senior Developer will decide each and every small
feature/component should be in each module.
★ Programming/Coding:
○ Here developers will start coding the application according to high
level design and low level design.
★ Testing:
○ After the entire application is fully created then it will be tested
against the requirement specifications. If there is any defect found in
the application the defect is fixed in this stage only.
★ Installation:
○ After creating and fixing all the defects the product is installed at the
customer place by the installation engineer.
★ Maintenance:
○ After installing a product at the customer location then the customer
starts using the application if he finds any issues or if he suggests
any small changes will be fixed by this maintinance stage only.
❖ Requirement Analysis:
➢ Here the testing team will go through the requirement document with
the functional and non functional details in order to identify the
testable requirements.
➢ In case of any confusion, the QA Team may set up a meeting with
clients and stakeholders(Technical leads, business analyst, system
architects and clients etc.).
➢ Once the QA team is clear with the requirement they will document
the acceptance criteria and get it approved by the customers.
❖ Test Planning:
➢ The Test Planning phase starts soon after the completion of the
Requirement Analysis Phase.
➢ In this phase QA Manager or QA Lead will prepare the Test Plan and
Test Strategy Documents.
■ Test Plan:Test Plan is a document which contains all the futute
testing activity to be done by the testing team in the entire
project.
❖ We use Test Plan for following Reasons:
➢ To complete the entire testing activity on time.
➢ To provide a quality product to the customer.
➢ To ensure maximum coverage and identification of defects in an
effective way.
■ Test Strategy:It is an outline that describes the testing
approach of the software development life cycle.It is created to
inform Project Managers, Testers and developers about some
key issues of the testing approach.
Types Of Testing:
➢ White Box Testing
➢ Black Box Testing
➢ Grey Box Testing
➔ White Box Testing:
◆ Testing the each and every line of the code in the application is
called White Box Testing.
◆ This testing is done by developers and also testing teams with a very
good knowledge on programming skills.
◆ White Box Testing also contains:
● Path Testing
● Condition Testing
● Loop Testing
◆ Path Testing:
● Here we write the flowgraphs and we will test each and every
individual path.
◆ Condition Testing:
● In this we test the condition statement for both true and false
values.
● For testing the conditional statement first will pass true
values.statement1 should be executed.
● Then we will pass a false value statement 2 would be
executed.
◆ Loop Testing:
● In loop testing we test the programme for each and every cycle
of the loop.
➔ Black Box Testing:
◆ Testing the features of the application without looking at the source
code of the application is called Black Box Testing.
➔ There are different types of Black Box Testings:
◆ Functional Testing:
● Testing each and every component of the application with all
the possible valid and invalid scenarios is called Functional
Testing or Component Testing.
➔ Regression Testing:
◆ Testing the unchanged features due to changes done in some other
features is called regression testing.
➔ Types of Regression Testing:
◆ Unit Regression Testing
◆ Regional Regression Testing
◆ Full Regression Testing
➔ Under Testing:
◆ Testing a component for less than the required no.of scenarios is
called Under Testing.
◆ In Under Testing we may miss defects for the missing scenarios
➔ Over Testing:
◆ Testing a component for more than the required no.of scenarios is
called Over Testing.
◆ Through Over Testing we will waste a lot of time and we may lack
time to test other components.
➔ Optimized Testing:
◆ Testing a component for the exact no.of required scenarios is called
Optimized Testing.
AGILE:
❖ AGILE is one of the SDLC models.
❖ Agile is the fastest way to respond to a customer.
❖ Agile is derived from the spiral model.
❖ In Agile there are deadlines for each cycle.
❖ Agile methodology promises any application that can be developed in 7 or 15 or
30 days with 7 +/- 2 members.
Agile has 2 types:-
➔ Scrum Method(99%)
➔ Extreme Programming(1%)
◆ Requirement Collection
◆ Feasibility study
◆ Design
◆ Coding
◆ Testing
◆ Installation
◆ Maintenance
➔ Keywords in Agile:
◆ Product Owner:
● He is a business analyst who has complete knowledge on the
product.
◆ Scrum Master:
● He is a Product Manager who manages the team and makes sure
tasks assigned by the Product Owner are completed on time.
◆ Product Backlog:
● “Requirements Prioritized” by the customer or project manager is
called “PRODUCT BACKLOG”.
◆ Sprint Backlog:
● Set of requirements for a particular sprint is called “Sprint Backlog”.
◆ Carry Forward:
● The changes taken from the sprint to next sprint is called “Carry
Forward”.
◆ User Stories:
● Set of requirements given by the customer is called “User Stories”.
➔ What is SPRINT?
◆ SPRINT is the Time Interval or Time Frame in which work has to be
completed and make it ready for the review or deployment to
production.The sprint time duration can be range within 2 weeks to 1
month.
➔ What is Story Point?
◆ Story Points are the quantitative indication of complexity of a user story.
◆ It is based on the story point that all the efforts of the story will be
determined.
◆ A story point is relative and it is not absolute.
◆ For example to implement a story the development team may need to
change only a few lines of the code but the testing team may have to test in
different places.
➔ What is EPIC?
◆ EPIC is nothing but the user stories which are not defined and kept for
future sprints.
What is the difference between Mobile Device Testing and Mobile Application
Testing?
❏ Mobile device testing means testing the Mobile Device and Mobile
Application Testing means testing the Mobile Application on a Mobile
device.
What are the different types of Mobile Applications?
★ There are 3 types of Mobile Applications.
○ Native Applications
○ Web Applications
○ Hybrid Applications
➔ Native Applications:
◆ Native apps are installed from applications stores like
Android’s Google Play store and Apple’s App store. The
application which can be installed into your devices and run is
known as Native Applications. For ex:Whatsapp and Angry
Birds
➔ Web Applications:
◆ Web Applications run from mobile browsers like
Chrome,Firefox,Safari and Opera etc., using Mobile network or
wifi. Ex:Facebook.com, gmail.com, yahoo.com
➔ Hybrid Applications:
◆ Hybrid Applications are a combination of Native and Web
Applications. They can run on devices or offline and are
written using web technologies like HTML5 and CSS. For ex.
Ebay, Flipkart etc.,
What are the different Defect Tracking tools used for Mobile App Testing?
❏ Bugzilla, Jira, QC and Rally
What are all major networks to be considered while performing application testing?
❏ We should test the application on 4G,3G,2G and wifi.2G is a slower network.
When performing a sanity test on the mobile application what all criteria should be
taken into consideration?
❏
ADB COMMANDS:
❖ What is an ADB?
➢ Android Debug Bridge
AWS
AWS:
❏ AWS is a secure Cloud Services platform, offering compute power,
database storage and Content delivery. Running web and application
servers in the cloud to host to dynamic websites.
What are the key components of AWS?
★ ROUTE 53
★ Simple Email Service
★ S3 or Simple Storage Device
★ Elastic Compute Cloud(EC2)
★ Elastic Block Store(EBS)
★ Identity and Access Management
★ Cloud Watch
○ ROUTE 53:
■ A DNS Web Service
○ Simple Email Service:
■ It allows sending email using Restful API or via regular SMTP
○ S3 or Simple Storage Device:
■ It is a storage device and most widely used AWS Service
○ Elastic Compute Cloud(EC2)
■ It provides on demand computing resources for hosting
applications.It is handy incase of unpredictable workloads.
○ Identity and Access Management:
■ It provides enhanced security and identity management for
your AWS account.