Photo by Priscilla Du Preez on Unsplash

Whether you are a developer, QA, or anyone who reads the user story to understand what and why are we building, should know what a good user story looks like …

The user story is a term vastly used where the company claims to be using agile methodology. The user story is usually a sentence or two that describes a small piece of functionality that provides business or customer value.

Imagine you are being asked to review the user story or when a user story is refined as a team, how you will provide feedback that the user story has…


Photo by Dakota Roos on Unsplash

The below framework can be used as a guideline to define user stories.

  1. A good user story should describe the problem that we are trying to resolve rather than offering a solution to the problem
  2. It should focus on the outcome rather than the output
  3. To create empathy, the user story should have a specific persona rather than a faceless user
  4. It should also point towards a business or customer value that will be achieved if we implement this specific user story
  5. The user story should follow INVEST (A user story should be Independent, Negotiable, Valuable, Estimateble, Small, and Testable.)

DoD checklist

Why you need a Definition of Done(DoD)?

According to the Scrum Guide:

The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current definition of “Done”.

Development Teams deliver an Increment of product functionality every Sprint. This Increment is useable, so a Product Owner may choose to immediately release it.

For a scrum team to deliver the product which can be used by the end users , they need to answer the following

  • How the team has decided that the developed functionality ready to be shipped?
  • What will give the Product Owner confidence to make the decision for…

Photo by Krzysztof Niewolny on Unsplash

Found an issue during a sprint! Put it in the backlog
Sound familiar?

Above is a common response when a bug has been found during the sprint. Following the approach to dump everything in backlog results in an overwhelming backlog that’s difficult to contain. Managing bugs than can easily spiral out of control.

According to Wikipedia: “A software bug (or defect) is an error, flaw, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways. …


How much test automation is required at different levels of SDLC?

Testing Pyramid

The testing strategy describes the software development testing approach. It captures the technique of how we test the product and achieve the testing goals throughout the SDLC. Usually, test strategy is defined on an organizational level in order to manage the stakeholder's expectation.

The challenge is how much do we have to unit, integration, functional or manual test our application? How much to automate? How to write tests that provide test coverage but also helps in determining root cause analysis of the bugs?

Testing pyramid can answer all of…


In the book, Agile Testing: A Practical Guide for Testers and Agile Teams, Lisa Crispin and Janet Gregory distilled Agile testing principles as below.

  1. Provide continuous feedback: Agile testing provides continuous feedback about how a product meets the business needs and distribute test results. Stakeholders regularly receive feedback regarding quality from agile testers.
  2. Deliver value to the customer: The end goal of every action taken by an Agile tester is to create the best product possible for the customer. Since customers are exposed to their products during development, they can update requirements as development progresses. …


Photo by David Travis on Unsplash

Agile manifesto and its correlation with testing

Agile testers are involved in the requirements, design, and development of the project and have constant interaction with the entire team ( including developers, fellow testers, business analysts, scrum master, and product owners).

They are co-owners of the user stories, and their input helps build quality into the product instead of checking for quality in the end. They need to collaborate with the programmer team to share the scenarios and try to identify the defects at the unit level itself. This practice will contribute towards preventing the bugs rather than finding the bug and then fix it.

All processes and…


Photo by Charles Deluvio on Unsplash

All you need to know before starting Mobile app testing

Both the test strategy and test planning needs to ensure that the app available to the end-users is of the highest quality. With almost more than 4 million mobile apps available for download the highly-competitive supply and demand mean as a tester we must ensure that the quality, usability, and security of your mobile app not only meets expectations but exceeds them.

CHECKLIST

Some applications are targetted for specific platforms or specific devices. Each app will have a different client requirement for versions to be supported. For better test coverage, make…


Photo by Romson Preechawit on Unsplash

3 steps bug prevention strategy before code deployment to test environment

During the development process, it is more cost-effective and efficient to fix bugs in earlier stages rather than later ones. The cost of fixing an issue increases exponentially as the software moves forward in the SDLC

What's more efficient and cost-effective to fix a bug before its deployment to a later stage from the local environment.

Below mentioned strategies can help in defect prevention in local environment

All the team members should actively participate in sprint planning so that there is no space for ambiguity and then they can…


Photo by Caspar Camille Rubin on Unsplash

What is an API and rest API? What needs to be tested in API and generic test cases for API testing

What is an API?

An API or Application Programming Interface is a set of routines, protocols, and programming instructions for accessing a web-based software application.

REST stands for Representational State Transfer. Representational state transfer is a software architectural style that defines a set of constraints to be used for creating Web services. Web services that conform to the REST architectural style, called RESTful Web services, provide interoperability between computer systems on the Internet. (Source: Wikipedia)

According to Mike Cohn’s famous Test Pyramid, API tests lies at the service level (integration), which suggests that around 20% or more of our tests should focus on API…

Passion for QUALITY PRODUCT

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store