Testing for StartUps is very different than testing for big businesses. Mostly, because of the lack of funds and time to market – which are common constraint across the globe. But most importantly, because the startups are mostly pivoting, if not completely, then in parts. Their feedback cycle have to be super-efficient and really quick. Users are directly involved and lot of monitoring and user metrics decide the way forward for the product.

When testing for such fast moving startups , one needs to strategize smarter with their time, funds and tools. The approach taken is indeed out of the box sometimes. Unlike, existing businesses where the end goal is defined, startups are lot of times open to a new end, which is more glorious than what they had originally planned for. (This may sound like machine learning has been inherently applied.)

The ideas and responses will be radically different and pretty disruptive, for some routine questions for developing the test approach, in case of a startup- Why are we testing, what are we testing, Who will test, what will get impacted, how to test, which tools can help, what metrics are the business measuring, how much time do we have….

Learn to test for startups in the coolest and most efficient way. Be useful to your business.

 
 

Outline/Structure of the Workshop

1. Understanding key goals of testing for startups and metrics that measure its success and how different they are from testing for big or routine businesses.

2. Understanding key fundamentals and influencing factors in startups vs. big businesses.

3. Role of testing and testers. What kind of testing is critical - how and which open source tools can be implemented rightaway.

Tips n Tricks - Seek support from organisation / Collaborate with other teams / Get metrics, monitor them / Monitor logs / Get developers to test / Test in production / UX testing. Involve users.

Learning Outcome

  1. Testers will understand why it is different to test in startups? And what is really critical to startups from testing point of view.
  2. What are the key inputs testers should look at while building their approach to test for startup? How much more agile testers have to be and the startups too.
  3. Free/Opensource Tools and tips that help fasten the testing process for startups.

Target Audience

Testers, Test Leads/Managers, Product Managers

Prerequisites for Attendees

Not much in specific - Basics of testing should be good.

schedule Submitted 8 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Robin Gupta
    By Robin Gupta  ~  6 months ago
    reply Reply

    Brilliant topic and proposal.

     

    If we could add a dash of automation, this could help a lot of testers/automation engineers/developers in the Startup world.

    • Smita Mishra
      By Smita Mishra  ~  6 months ago
      reply Reply

      Dear Robin,

      Thanks for your compliment.

      There will be more than just a dash of automation. We will be discussing automation tools and approach to automation and basis to judge what works best and how to figure it out.

      As you pointed out - the idea is to help a lot of testers / automation engineers / developers in the Startup world.

      Warm Regards,

      Smita

  • Pallavi ...
    By Pallavi ...  ~  7 months ago
    reply Reply

    Hi Smita

    It would be an interesting insight to understand the testing mindset for a startup , and the tools and technologies to consider. 

    I have a few questions although-

    a. are there any case studies where we can talk about certain startup implementing those "best startup testing practices" and they benefitted from it.

    b or common mistakes startups do with their testing teams - expectations/ process setting 

    c. is the model generic for any startup or the domain would be an influencing factor?

    • Smita Mishra
      By Smita Mishra  ~  7 months ago
      reply Reply

      Hi Pallavi,

      Thanks for your comments. Here are my responses :

      a. Yes - we have case studies and will share examples of 2-3 project work done.

      b. Yes - when we show what are same and what are different between testing for startups and established businesses, we will talk about common pitfalls and how to set expectations and handle the same for the team.

      c. Model is generic but when you follow it, there are threads that will lead you into some differences based on domains. We will be discussing these too.

      Please let me know if you have any more queries. Thanks again.

      • Pallavi ...
        By Pallavi ...  ~  7 months ago
        reply Reply

        Hi Smita

        Thanks for your answer, just two more

        a. will the model change for a web based startup vs a mobile app based startup etc.. ?

        b. have you shortlisted the domains you would be covering if that is a deciding factor in the model?

        Thanks

        Pallavi. 

        • Smita Mishra
          By Smita Mishra  ~  7 months ago
          reply Reply

          Dear Pallavi,

          Thanks for your interest and questions. My responses are here:

          a. Technology (and how users use it) is a key component in factoring the test approach and strategizing how to go about it. So, when we come to that - web based and mobile based apps - the test models will have some part common (wrt functional/business driven use case) and some part different (wrt test environment / h/w / UX / design / tools/compatibility...and many more). We will talk about it.

          b. We will be show casing examples of a healthcare app and a FinTech app. Besides this, for every aspect we discuss when building the test approach for startups, we will have an example from real world apps from the startup world vs big businesses - wherever applicable.

          Feel free to ask more. Thanks for your questions.

          Warm Regards,

          Smita

          • Pallavi ...
            By Pallavi ...  ~  6 months ago
            reply Reply

            Got it Smita, thanks.