Does your “Definition of Done” include “Automated tests” or does most of the QA work get carried forward sprint after sprint?<\/strong><\/p>\n

Most Scrum teams i.e. nearly 80-90 percent of them get into this phase at least once!! You are not Alone!<\/p>\n

Test Automation is a key factor to incorporate in any Agile teams. If you are spending a lot of time performing manual testing during every sprint, you are never going to get things “Done”.<\/p>\n

With manual testing in place in every sprint,<\/strong><\/p>\n

\n
• \n

  You may spend ‘n’ hours in Sprint-1<\/p>\n<\/li>\n

• \n

  n+3 hours in Sprint-2<\/p>\n<\/li>\n

• \n

  n+5 hours in Sprint-3 etc.<\/p>\n<\/li>\n<\/ul>\n

  The time spent testing new features and any changes to the existing features will increase the manual test effort. The amount of time spent on regression testing will also increase drastically.<\/p>\n

  By the time you decide to launch to the marketplace, the “testing effort may take weeks to complete”.<\/strong><\/p>\n

  Will automation help overcome this issue? Yes…<\/strong><\/em><\/p>\n

  \n
  • \n

    Identify tests that are repetitive or run frequently in the sprint, as they become the best candidate for automation. Automate simple tests.<\/p>\n<\/li>\n

  • \n

    Stay up to date with all the tests and get the product backlog items automated slowly and this will bring down the manual test effort gradually.<\/p>\n<\/li>\n

  • \n

    Have a well-defined “definition of done”.<\/p>\n<\/li>\n<\/ul>\n

    Why not Automate as early as possible?<\/strong><\/p>\n

    Get your Sprint 0 to do all the groundwork and shape up the test environment, strategy, tool selection, BDD, TDD etc…<\/p>\n

    Let the Developer and QA work on a story together….say you have 5 Acceptance Criteria for a story and it may take 3 days for the story to be completed.<\/em><\/p>\n

    \n
    • \n

      Dev \/ QA –> Work on AC-1 (acceptance criteria 1 from the feature)<\/em><\/p>\n<\/li>\n

    • \n

      Dev writes the code to cover AC-1 & QA writes the automated tests, prep test cases, test data for AC-1<\/em><\/p>\n<\/li>\n

    • \n

      Dev checks-in code for AC-1 & QA checks-in automated test code for AC-1<\/em><\/p>\n<\/li>\n

    • \n

      Let the CI (Continuous Integration) take care of the rest, tests are executed against the Dev code. Fully Tested and its “Done”<\/em><\/p>\n<\/li>\n

    • \n

      Continue the similar pattern for remaining Acceptance Criteria, AC-2 to AC-5.<\/em><\/p>\n<\/li>\n<\/ul>\n

      On the 3rd Day of the Sprint,<\/p>\n

      We have Dev “Done”, QA “Done” and Story\/feature is “Done” “Done” \ud83d\ude42<\/p>\n

      Avoid the “Mini Waterfall” or so-called waterfall-agile “W-Agile” approach that happens in the last few days of the sprint.<\/p>\n","protected":false},"excerpt":{"rendered":"

      Does your “Definition of Done” include “Automated tests” or does most of the QA work get carried forward sprint after sprint? Most Scrum teams i.e. nearly 80-90 percent of them…<\/p>\n","protected":false},"author":4,"featured_media":2649,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_price":"","_stock":"","_tribe_ticket_header":"","_tribe_default_ticket_provider":"","_tribe_ticket_capacity":"0","_ticket_start_date":"","_ticket_end_date":"","_tribe_ticket_show_description":"","_tribe_ticket_show_not_going":false,"_tribe_ticket_use_global_stock":"","_tribe_ticket_global_stock_level":"","_global_stock_mode":"","_global_stock_cap":"","_tribe_rsvp_for_event":"","_tribe_ticket_going_count":"","_tribe_ticket_not_going_count":"","_tribe_tickets_list":"[]","_tribe_ticket_has_attendee_info_fields":false,"footnotes":""},"categories":[1],"tags":[51,52,53,54,50],"yoast_head":"\n