Skip to main content

A Day in Software Tester's Life





Day 1: During the first day of the iteration, the highest priority stories are picked from the product backlog. The QA tester, along with the rest of the team members and the Product Owner, work to define the acceptance criteria for each user story. High-level questions are asked, and the acceptance criteria is written as part of each story.
In the second part of the planning session, the testing tasks for each story are identified and estimated. Some typical testing tasks are: “Define high level tests,” “Write automated tests,” “Perform manual exploratory testing,” “Write a GUI smoke test,” and “Generate test data.”
Days 2/3: On the 2nd and 3rd days of a sprint, the tester has conversations with the Product Owner to refine acceptance criteria for each story. The goal of these conversations is to elicit the details of what is expected from each feature. These conversations may go on the following day/s.
Also, during days 2 and 3 of a sprint, the Tester starts writing acceptance tests. This is a collaborative task that helps drive development as developers start focusing on writing code to pass the acceptance tests. The acceptance tests writing will span to the next few days. This process may also trigger new questions and new conversations with the Product Owner to clarify acceptance criteria.
Days 4/5: Days 4 and 5 are where exploratory testing typically begins, as the coding of the first stories may be completed. After making sure the “happy path” tests pass, the tester gets to use his creativity to discover conditions that no one may have thought of. Exploratory testing typically goes on until close to the end of the iteration.
Days 6/7: As soon as more of the stories are coded, the tester starts performing tests that verify combined functionality to make sure the new user stories that have been implemented integrate smoothly with the existing ones. This task will go on at least for a couple of more days.
Days 8/9: Assuming that the development of all the stories is done by the 8th or 9th day of the iteration, it is the time to run end-to-end tests that verify real-life scenarios. The goal of these tests is to check that all the new functionality increases the value of the software and it is ready for delivery.
Day 10: On the last day of the iteration, we demonstrate the stories to the Product Owner and get his or her acceptance. This demo usually requires some set up, like generating the appropriate data and making sure all the features are included in the demonstration. The whole team focuses on generating a polished version that can be presented to customers.

 References: 

Comments

Popular posts from this blog

Complete Selenium Topics to be a Professional Selenium Tester

Complete Topics in Selenium to be a Professional Tester Free PDF Below

SECTION 1: INTRODUCTION TO AUTOMATION TESTING
•        What is automation testing? •        When Automation Testing is needed? •        When Automation Testing is not needed? •        What is the use of automation testing? •        Different Automation Tools available in the Market. •        What is the difference between Selenium and QTP?
SECTION 2: INTRODUCTION TO SELENIUM
•        What is Selenium? •        Advantages of Selenium
SECTION 3: COMPONENTS IN SELENIUM
•        IDE Overview •        RC Overview •        Selenium-Grid •        Selenium Web Driver/Selenium 3.0
SECTION 4: SELENIUM IDE
•        Installing IDE •        IDE icons •        Recording your first test with IDE •        IDE Context Menu •        Assert •        Verify •        Adding IDE comments •        Synchronization commands •        Working on pages with AJAX •        Storing elements •        Creating test suites •        Tools  to identify elements/objects •        …

Good news for Software Testers

Here are some of the latest Testing and IT news from technical reporters –
IT managers consortium has agreed that software testers would no longer be blamed for a production defects. Though they are yet to find some one who they could put blame on (Johny the developer is said to be already suffering from ProductionDefectoPhobia)Consortium has also agreed on having salary of software testers on par with software developer at least by 2020. There was an unanimous decision on increasing management salary by 23% from immediate effectConsortium has barred developed from using phrase “It works locally”. Violation of this rule would attract 1 night out in office. Continuous violation would attract exponential salary deductionsComplete Topics to be a Professional Selenium TesterSelenium Concepts Speak and Automate—New era in automated testing. Voice Automation tool for web and windows application was released yesterday. This tool is capable of generating automation suites as you speak of appli…

Top 5 Selenium Webdriver Coding Tips to Improve Quality

SeleniumWebdriver is a powerful automation tool for testing web applications. It’s an open source library bundled with a rich set of features. Using it for testing a website is just like simulating the actions of a real user.
All these abilities together make it a perfect tool for automation. But you need proper guidance to get the best out of it. In this blog post, we’ve assembled some of the best and Top 5 Selenium Webdriver coding tips for software testers.




Tip-1: Best Method To Create Webdriver Instance.
It’s one of the most common Selenium Webdriver coding tips which you can’t avoid to use.
1.1- Use the <Factory> design pattern to create objects based on browser type.
1.2- Extend the below code or use it as is in your projects.
public class DriverFactory {
private WebDriver driver = null;
    public static WebDriver getBrowser(String browserType) {         if (driver == null) {             if (browserType.equals("Firefox"))
            {                 driver = new …