The Evolution Of Software Testing

Transformation from Traditional Software Testing to Agile Testing. Challenges during traditional approach and the added advantages of Agile Software Testing. New skills for an Agile Tester and some best practices in Agile Testing

 
1 favorite thumb_down thumb_up 6 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

—Introduction

—Traditional QA

—Challenges with Traditional QA

—The Emergence and Mechanics of Agile Testing

—New Skills for the Agile Tester

—The Tester and the Team

—Best Practices in Agile Testing

—Agile Testing Advantages

Learning Outcome

The target audience will be able to understand that how the complete software testing has evolved since its inception i.e. the traditional approach

Target Audience

Test Managers, Test Leads, Developers, Project Managers

schedule Submitted 10 months ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Rahul Sharma
    By Rahul Sharma  ~  10 months ago
    reply Reply

    Hi Sumeet,

    Do you have a basic slides ready to show? Would like to know what different kind of testing techniques you would be talking about?

    Regards,

    Rahul

    • Sumeet Kumar
      By Sumeet Kumar  ~  10 months ago
      reply Reply

      Hi Rahul,

      Yes, I've prepared a PPT on this topic and will share the same with you via email. And this topic of presentation covers the transformation from traditional testing to agile testing. I've not mentioned about any specific testing techniques in my presentation but it consists of the challenges which were there in traditional approach and how those challenges are overcome in agile testing. Then, it talks about the emergence and some of the best practices in agile testing. You could have a look into the PPT which I will share with you via email and that would give you a much clear picture on this.

      Regards,

      Sumeet Kumar

      • Rahul Sharma
        By Rahul Sharma  ~  10 months ago
        reply Reply

        Thanks Sumeet. Did you already send it?

         

        Regards,

        Rahul

        • Rahul Sharma
          By Rahul Sharma  ~  10 months ago
          reply Reply

          Thanks Sumeet for sending the PPT. Would like to ask somethings around QA and Testing - 

          1. Do you feel QA and Testing are same thing?

          2. QA is performed by separate organization? Is thats the case always?

          3. In "QA writes test plans", "delivered to QA for testing",  "QA reports defect" and "another version to QA", QA is mentioned as a person, but its actually a job if we go by definition (Quality Assurance)

          4. "QA reports defects back to development".....development what?

          5. You have mentioned QA team and Development team, do you feel there should be two different teams for the same product?

          6. In the diagram on 10th slide, could not understand meaning of box "cant read PPT"

          7. In the diagram, you have mentioned "daily status meeting". Are you referring to "daily stand ups or scrums"?

          Regards,

          Rahul

          • Sumeet Kumar
            By Sumeet Kumar  ~  10 months ago
            reply Reply

            Hi Rahul,

            Thanks very much for your valuable feedback/review comments. Please find below my answers to the corresponding comment:

            1. QA and Testing both are quite different from each other by definitions. However they are used interchangeably based on the contexts but that's not the ideal way of using it. QA (Quality Assurance) is the holistic term and Testing is a part of it.

            2. Looking at the earlier days where traditional approaches were used in software development, then 'Yes' as QA used to be performed by separate organization. And the rationale behind that approach used to be the increased probability of finding more number of defects. But that's not always the case as we can see in current scenario where customers want it to be performed by same organization without compromising on the quality of the product. And as the things have become more transparent, hence customers can review the product time to time and provide their feedback on the product.

            3. That's mentioned incorrectly. It should have been appended by 'team' rather than just 'QA'. I will correct it and mention it as 'QA team'.

            4. That's mentioned incorrectly. It should have been appended by 'team' rather than just 'development'. I will correct it and mention it as 'development team'.

            5. Looking at the traditional approaches of software development, there used to be separate QA and Development teams. But, now in the current scenario we've come up with the 'Feature team' concept which is cross functional teams. There is no separate testing and development team, all are part of a particular feature team which works towards building, testing and delivering a feature which adds value.

            6. That's mentioned incorrectly. It should have been mentioned as 'Product Backlog Grooming'. I will correct it.

            7. It's 'Daily Stand-up Meetings'. And I think both 'Daily Stand-up Meetings' and 'Daily Scrum Meetings' refer to the same agenda which talks about - What a person did since the last stand-up meeting? What a person will do until the next stand-up meeting? What are the blockers or impediments faced by a person?

            Please correct me if I've understood or mentioned anything wrong here. I will make the necessary updates to my PPT.

            Regards,

            Sumeet Kumar

            • Rahul Sharma
              By Rahul Sharma  ~  10 months ago
              reply Reply

              Thanks Sumeet for clarifications.