Agile testing

Agile software development allows the team to work together more efficiently and
effectively in developing projects.

Close communication with customers to understand the features.

The customers get a look and feel of the project progress at the end of each
iteration/sprint and we get constant feedback so that dev tream responsive to the
changing requirements and can accommodate changes as per client feedback

This helps to avoid the cost of rework at a later stage

Disadv

Sometimes, at the beginning of the projects, the requirements are not crystal clear. The
teams might proceed and find that the customers’ vision got realigned and in such
situations, the teams need to incorporate many changes

Scrum
Scrum is one of the frameworks by which you can implement agile
SCRUM is a process in agile methodology which is a combination of the Iterative model
and the incremental model.

An easier way to remember all of this is to memorize the 3-3-5 framework. It means that a
scrum project has 3 roles, 3 artifacts, and 5 events.

These are –
Roles: PO, Scrum master, and development team.
Artifacts: Product Backlog, Sprint Backlog and Product increment.
Events: Sprint, Sprint planning, Daily Scrum, Sprint review and Sprint retrospective.

Scrum team
comprise of developers, testers along with the product owner and a scrum master

Sprint
time frame in which the planned work has to be completed and make it ready for review

product ownwer
product owner is the person who represents the customer side and key stakeholder of the
application to be developed
Managing and prioritizing the product backlog

Scrum Master
makes sure that the scrum team is productive and progressive. In case of any roadblocks,
scrum master follows up and resolves them for the team.
User Story
User stories are nothing but the requirements or feature which has to be implemented.

Testing team bases their test cases/conditions on these acceptance criteria.

Product Backlog
The product backlog is a kind of bucket or source where all the user stories are kept. This is
maintained by the Product Owner

Sprint Backlog
Based on the priority, user stories are taken from the Product Backlog that has to be
implemented in that particular sprint.

Story Points
Story points are a quantitative indication of the complexity of a user story. Based on the
story point, estimation and efforts for a story are determined.

burndown chart

A burndown chart shows the amount of work that has been completed in a sprint,
and the total work remaining

Velocity
The total number of story point which a scrum team archives in a sprint, is called Velocity

Scrum ceremonies
Sprint Planning Meeting
A planning meeting is the starting point of Sprint. It is the meeting where the entire scrum
team gathers, the SCRUM Master selects a user story based on the priority from the
product backlog and the team brainstorms on it.

Daily Standup
During the sprint cycle, every day the scrum team meets for, not more than 15 minutes
(could be a stand-up call, recommended to have during the beginning of the day) and state
3 points:

1. What did the team member do yesterday?

2. What did the team member plan to do today?
3. Any impediments (roadblocks)?
It is the Scrum master who facilitates this meeting.

Review Meeting
At the end of every sprint cycle, the SCRUM team meets again and demonstrates the
implemented user stories to the product owner. The product owner may cross verify the
stories as per its acceptance criteria.

The retrospective meeting happens after the review meeting.

Retrospective Meeting
The SCRUM team meets, discusses & document the following points:

 What went well during the Sprint (Best practices)?

 What did not go well in the Sprint?
 Lessons learned
 Action Items.
The retrospective meeting helps to implement the continuous improvement of the SCRUM
process.

What is Test Design? When to create Test Design?

 Basically test design is the act of creating and writing test suites for testing a
software.
 Test analysis and identifying test conditions gives us a generic idea for testing
which covers quite a large range of possibilities. But when we come to make a
test case we need to be very specific

After the test conditions are defined and sufficient information is available to create
the test cases,test design can be created.

Differences between Test Case and Test Scenario

Here, are significant differences between Test scenario and a Test Case

Test ScenarioTest Case

A test scenario contains high-level documentation which describes an end to end

functionality to be tested.
Test cases contain definite test steps, preconditions, data, expected results for testing all
the features of an application.

It focuses on more “what to test” than “how to test”.

A complete emphasis on “what to test” and “how to test.”.

Cross Browser Testing

It is the process of verifying your application’s compatibility with different browsers.

What to Test?
1. Base Functionality: Links, dialogs, menus etc.
2. Graphical User Interface: Look and feel of the application.
3. Response: How well the application responds to user actions.
4. Performance: Loading of the pages within allowed the time frame.
Can be done manually or automation

It ensures user get a seamless experience of the application, irrespective of the browser
that they are using

Anup

Suppose if there is a functionality for zip code box,

once you enter the zipcode and click on next button redirects you to next page

What are the test cases can be created for this?

Below questions were asked

Anup:

Tell me about your work experience

How will you test pixel size of an image on mobile
How will you test color of a text box on browser testing apart from just looking at it?
Next asked what do we call this type of testing.
Suppose actual color (on UI screen) of edit box is red but element property color shows as blue.
What will you do if this mismatch happens?
I said we raise the defect
Next asked about defect life cycle
Who decides the defect priority and severity
Your experience in API Testing
How did you used Postman in your previous project?
Headers used in API testing
Any experience in SOAP testing?

Ayaz
What are Smoke and regression testing?
What you will do if there is incomplete requirement
What will you do if there is any conflict between you and dev team on requirement
understanding?
What is a test case and what details it has?
Test case tools used in previous experience
Have you used Qtest?
What you will do if you are not able to complete the work on time?

Test case tools used in previous experience

have you used QTest