How do you start testing ?

Requirement Analysis : I start my testing from the Requirement gathering phase . I review the
requirements so that i can be clear on what needs to be done. I review designs and ask any valid
questions to get better clarity and understanding of the functionality
Test Planning : i plan the approach to test it. I decide the environment and types of testing required to
test that feature .

Test Case Creation : After that i start developing Testcases, create checklist. And prepare environment
for test execution.

Test Execution : Once the build is deployed. I start executing testcases and reporting bugs with all steps
to reproduce, bug priority and videos and screenshots of bug so the dev can comvinently reproduce it.

Once the development team fixes an issue, I retest the functionality of the product, and perform
regression testing to ensure that the software still works correctly after all of the changes have been
made.

Once all of the fixes have been changed, and all planned tests have been executed, I prepare the test
closure document. This document is a summary of all the tests performed during the software
development life cycle.

How you report bug?

First i write title of the bug which will state exactly what is happening.

Description is short summary of what the problem is.

Steps to reproduce.

The steps should be through and easy to reproduce.

Actual and expected results

I give urls and screenshots and supporting imformation

I also set priority of the bug

Environment and devices where the bug was found.

I will also evaluate and describe the severity and priority of the bug on that bug report.

Tell some of the qualities A QA must have ?

Test Case : A test case is a set of instructions on “HOW” to validate a particular test objective/target.
bug priority ? determines how important is the bug to be fixed.
Severity ? determines how much this bug is impacting the Application
regression
How you give go ahead to testing ?

I will ensure all the requirements are covered with the help of test coverage
metrics.
For Defects i verify that :
All Blockers are fixed and No known Critical / Severity 1 defect is in Open Status.
All High Priority defects are identified and fixed
All High Priority defects are re-tested and closed and corresponding Regression
scenarios are successfully executed.
For Test Cases i verify that :
Complete Functional Coverage is achieved.All major functional / business flows
are executed successfully with various inputs and are working fine.
All critical Test cases are passed.

How to write a Test Plan

You already know that making a Test Plan is the most important task of Test Management Process.
Follow the seven steps below to create a test plan as per IEEE 829

Analyze the product

Design the Test Strategy

Define the Test Objectives

Define Test Criteria

Resource Planning

Plan Test Environment

Schedule & Estimation

Determine Test Deliverables

Qualities of QA :

The most importnat characteristics a QA should have is Analytical and Creative thinking.
A QA should be able to think outside the box and understand the requirement to define a clear
strategy.

1. QA should know how to ask questions to To understand the product from other perspectives like
development, business, etc.
2. Qa should be able to Create number of Ideas

3. QA should be able to You Are Able To Co-relate Real-time Scenarios To Software Testing

4. QA should have good communication skills.

5. QA should be able to analyse Data and priorities.

Being a tester, you are not expected to do testing only. You need to understand the data collected from
testing and need to analyze them for the particular behavior of application or product

A/B Testing :
A/B testing also known as split testing or bucket testing. It is used to compare two version of a Web page
or App to determine which one performs better.

Beta testing :
Beta version of the App is given to the limited number of end users to obtain their feedback on product
quality. It helps to minimise the product failure risk and increase the quality of the product through
customer validation.

End to End Testing :

It means testing of the Application's workflow from the beginning to the end. It verifies all the
components of the system are able to run and perform under real work scenerios.

Can you explain the role of SQA in the software development process?

Software Quality Assurance (SQA) is a process used to ensure that developed software meets or exceeds
customer expectations and is free of defects. SQA activities include the creation of a test plan, the design
and execution of tests, and the tracking and reporting of defects. SQA is typically carried out by a
dedicated team, but may also involve participation from developers, project managers, and other
stakeholders. The goal of SQA is to identify and resolve issues before the software is released to
customers, resulting in a higher quality product. SQA is an important part of the software development
process, as it helps to ensure that software meets its intended purpose and does not contain errors that
could lead to costly and time-consuming problems.

How to prioritise and plan testing activities ?

Prioritizing and planning testing activities is an important part of Software Quality Assurance (SQA).
There are several factors that can be used to prioritize testing activities, including:

Risk: Test activities that address high-risk areas of the software should be given priority. This includes
areas where defects could have a significant impact on the software's functionality or on the user's
experience.

Business criticality: Testing activities that are critical to the success of the business should be given
priority. This includes areas of the software that are essential for the business to function, such as
financial transactions or customer data.

Test coverage: Testing activities should be prioritized to ensure that all aspects of the software are
covered. This includes functional, performance, security, and other types of testing.

Schedule: Testing activities should be scheduled to ensure that they are completed in time for the
software's release. This may require prioritizing activities that can be completed quickly over those that
take longer.

Once testing activities have been prioritized, they can be planned using a test plan. A test plan outlines
the overall testing strategy, including the types of testing that will be performed, the resources that will
be required, and the schedule for completing the testing activities. The test plan should also include a
risk management plan that identifies potential risks and outlines strategies for mitigating them.

It's also a good practice to use a test management tool, that will help you to organize, schedule and track
all the testing activities, and also will help to identify and prioritize the defects.
What do you do if you disagree with someone at work?
What is your most important career accomplishment? Why?