Monthly Archives: September 2015

Tester’s role in Scrum/Agile Team

In today’s competitive environment, Everybody wants to be ahead of Others. So is the case with the Organizations which want to offer there services with lesser time to market to end customer with less cost & better quality. In order to achieve this, Organizations are moving towards Agile methodology seeing more benefits over waterfall or other methodologies.

In a agile environment, development is carried out in short sprints. Scrum Teams work independently during the sprint to move ahead with development. Now, the question comes who all comprises Scrum Team. The Answer is Developers, Testers, Business Analyst, Designers. Every person plays an important role in making sprint a Success.

Scrum Methodology

When a sprint starts, Product Owner shares his wishlist with scrum teams & based on time estimates & capacity within the team, items are selected for development. So, Developers starts working on the items while Testers need to perform requirement analysis to find if there are any gaps in the requirement. Along with it, Test Planning, Test case Development, Test Data & Test Environment setup needs to be done before Development items are Ready for Testing. This means Testers work in parallel with developers on the feature to be developed. By the mid of sprint, Testers start receiving features for testing. If there are bugs, they get resolved within the sprint. Unless there are more bugs which can’t be fixed in the same sprint, Feature is developed & tested and is ready for sign-off from PO (Product owner/ Client) . After sign-off, features are Deployed at the end of sprint.

So a tester should not feel that his/her role will come once features are ready for testing. They need to start the work the moment sprint starts. Testers involvement from the start of development helps to identify issues earlier rather than later in the development phase which helps saves Time & Money.

I hope I was able to clear the doubt regarding testers role in Scrum Team. Still if anyone has a questions, please ask. I will be more than happy to answer them.

Difference between Test Case and Test Scenario

Every tester has to write test cases or Test cases as well as Test Scenarios depending upon the depth of documentation being followed in there respective organization. Some times, it becomes difficult for some one new to understand the difference between them so lets understand what exactly is Test Case & Test Scenario.

Test Scenario basically means a flow which a user can follow. A single Test Scenario can have multiple Test Cases but vice versa is not True. Lets understand with an example. User logging into website is scenario because this is a flow.

Test Case is a subset of Test Scenario. All test cases are derived from Test Scenarios. Taking the reference from example above, we can have following test cases:

  1.  Login using Correct credentials on website
  2.  Login using Incorrect username.
  3.  Login using Incorrect password.

Similarly, we can have more Test cases to check for Validation of input fields

  1.  Test for validation of username field to accept only valid email address (assuming username used on website is a email address).
  2.  Test for size limit of password
  3.  Test whether special characters are accepted as password
  4.  Verify blank spaces are not accepted as password
  5.  Verify blank password field is not accepted.

These are not the only test cases we can have. As a tester, we need to always strive to break the system in order to become better tester & increase our understanding about Application under Test. 🙂

Welcome To QATesters.in

I have started this blog to share latest news into Software testing field , How to series on Various Testing tools like Selenium, Cucumber, QTP, Jmeter along with working examples.

The vision of this blog is to help new comers in to software testing field to understand Testing principles & make there career in this field. Also for experienced testers to brush up there skill sets. It is a very exciting field to work on if person has willingness to learn new technology. In IT, the only thing which is constant is CHANGE. So, lets target to learn continuously about our Profession. I will be writing a blog post every week initially & will try to reduce sprint duration of post to post per Day 🙂 . Visitors of the website are more than welcome to share there insights, share there knowledge with rest of us. 🙂