How to deal with or prevent idle in the test team?












4















I'm currently in two scrum projects. The team consists of 9 people (5 developers, 3 testers). We work with user stories, story point estimates and two-week sprints. The team has received a great deal of Scrum and delivers reliably finished (Code + Test + Documentation) software. The test automation is up to date, and the CI runs through every day. However, this does not result in enough tasks for the test team.



Nevertheless, we have the following problem:



At the beginning of the sprint it always takes until testable user stories are completed. Therefore, it comes to idle with the testers, because there is nothing to test.



Already taken countermeasures (which could not solve the problem):




  • Testers begin with the test preparation for all stories


  • Support testers - where possible - the work of the developers


  • "Open Issues List" by the team in case someone has nothing to do


  • Know How Transfer among the testers



Nevertheless, we have not gotten the problem under control so far.
Question: Has anyone had similar experiences? What can you do about it?
I am grateful for all suggestions!










share|improve this question























  • Are all developers full time on the project? Are all testers full time on the project?

    – user3067860
    2 hours ago
















4















I'm currently in two scrum projects. The team consists of 9 people (5 developers, 3 testers). We work with user stories, story point estimates and two-week sprints. The team has received a great deal of Scrum and delivers reliably finished (Code + Test + Documentation) software. The test automation is up to date, and the CI runs through every day. However, this does not result in enough tasks for the test team.



Nevertheless, we have the following problem:



At the beginning of the sprint it always takes until testable user stories are completed. Therefore, it comes to idle with the testers, because there is nothing to test.



Already taken countermeasures (which could not solve the problem):




  • Testers begin with the test preparation for all stories


  • Support testers - where possible - the work of the developers


  • "Open Issues List" by the team in case someone has nothing to do


  • Know How Transfer among the testers



Nevertheless, we have not gotten the problem under control so far.
Question: Has anyone had similar experiences? What can you do about it?
I am grateful for all suggestions!










share|improve this question























  • Are all developers full time on the project? Are all testers full time on the project?

    – user3067860
    2 hours ago














4












4








4








I'm currently in two scrum projects. The team consists of 9 people (5 developers, 3 testers). We work with user stories, story point estimates and two-week sprints. The team has received a great deal of Scrum and delivers reliably finished (Code + Test + Documentation) software. The test automation is up to date, and the CI runs through every day. However, this does not result in enough tasks for the test team.



Nevertheless, we have the following problem:



At the beginning of the sprint it always takes until testable user stories are completed. Therefore, it comes to idle with the testers, because there is nothing to test.



Already taken countermeasures (which could not solve the problem):




  • Testers begin with the test preparation for all stories


  • Support testers - where possible - the work of the developers


  • "Open Issues List" by the team in case someone has nothing to do


  • Know How Transfer among the testers



Nevertheless, we have not gotten the problem under control so far.
Question: Has anyone had similar experiences? What can you do about it?
I am grateful for all suggestions!










share|improve this question














I'm currently in two scrum projects. The team consists of 9 people (5 developers, 3 testers). We work with user stories, story point estimates and two-week sprints. The team has received a great deal of Scrum and delivers reliably finished (Code + Test + Documentation) software. The test automation is up to date, and the CI runs through every day. However, this does not result in enough tasks for the test team.



Nevertheless, we have the following problem:



At the beginning of the sprint it always takes until testable user stories are completed. Therefore, it comes to idle with the testers, because there is nothing to test.



Already taken countermeasures (which could not solve the problem):




  • Testers begin with the test preparation for all stories


  • Support testers - where possible - the work of the developers


  • "Open Issues List" by the team in case someone has nothing to do


  • Know How Transfer among the testers



Nevertheless, we have not gotten the problem under control so far.
Question: Has anyone had similar experiences? What can you do about it?
I am grateful for all suggestions!







manual-testing test-management team-management management scrum






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 11 hours ago









MornonMornon

1168




1168













  • Are all developers full time on the project? Are all testers full time on the project?

    – user3067860
    2 hours ago



















  • Are all developers full time on the project? Are all testers full time on the project?

    – user3067860
    2 hours ago

















Are all developers full time on the project? Are all testers full time on the project?

– user3067860
2 hours ago





Are all developers full time on the project? Are all testers full time on the project?

– user3067860
2 hours ago










4 Answers
4






active

oldest

votes


















7















"there is nothing to test"




That is a strong statement.



I like to use James Bach's definition of testing:




Testing is the process of evaluating a product by learning about it
through exploration and experimentation, which includes to some
degree: questioning, study, modeling, observation, inference, etc.




So, unless there is nothing new to learn about the product, yes, you don't have anything to test.



However, there may be some new things that you can learn. Maybe if you do some of the following, you may uncover them:




  • Pair programming (yes, with the developer);

  • Investigate results of your monitoring and logging instrumentation;

  • Extend your monitoring and logging instrumentation;

  • Create chaos in your environments;

  • Refine backlog to remove duplication and increase simplicity;

  • Watch users (control groups or real ones) using your product;


  • Investigate competitors systems;

  • Refactor any piece of code (production code, automated checking code, deployment code, etc).


These activities may put a tester in new places, expanding his/hers understanding of the product.






share|improve this answer
























  • Most of the points have been completely implemented in the past few weeks. We are currently setting up Penetration Testing on a CI basis for our projects. Further education in the team are also on the agenda.

    – Mornon
    9 hours ago



















4














If you have a set of Regression Tests, testers can start automating them starting with which are easiest to automate. This will save you a lot of time in the long run during Regression Testing. Of course, this requires some programming skills and if the testers do not have those at the moment then this is the great time for them to learn it and apply to automating the tests. This is a win-win for both the testers and the team. As, testers are adding a new skill to their personal tool-set which will eventually benefit the business/company too.






share|improve this answer
























  • The test automation is up to date, and the CI runs through every day. However, this does not result in enough tasks for the test team. We have also offered training courses and so the testers just trained in Selenium.

    – Mornon
    11 hours ago











  • We are already implementing our CI on Penetration Test, and we are training our testers in terms of safety.

    – Mornon
    11 hours ago











  • @Mornon That's great! Not sure what else can be done. I personally tend to help out on some low priority development tasks.

    – Baljeet Singh
    10 hours ago



















4














In addition to some of the other suggestions, you could consider a few other options:




  • Build/run load tests for new/recent work (given the maturity of your test automation you may already have this under control)

  • Review existing test automation for obsolete or ineffective tests (You have no idea how much I wish I could reach this point)

  • Review and refactor existing test automation code. In any rapid development environment, automated test code can get dated quite quickly.

  • Review and update older customer documentation. In my experience this can become out of date fairly rapidly if development is quick.

  • Review other documentation to make sure it's up to date. This can include (but is not limited to) use cases, business requirements, database dictionaries, functional requirements, test documentation...

  • Work with product owners to refine any stories in the backlog - or just go in there and review them and ask questions anyway. Testers typically have a unique combination of breadth and depth with a product they're familiar with and can often pick up potentially problematic changes before they go to code.

  • Review the user stories and defects in the current sprint and start planning how to test them. If there's configuration that's needed, it can save a lot of time to set up as much of the configuration as possible before the story/defect is coded.


A lot of these are things I've done when I found myself in a holding pattern.






share|improve this answer































    1














    Since you mentioned, it's a scrum.. its actually the scrum master role to make a deliverable level module to prepare from tiny user stories, so that tester can start preparing their test case based on the deliverable level.



    Say for example, if a micro service which cannot be tested, it should not be included alone in the sprint, rather connecting module (frontend or api) should be included.speak to your scrum master, ask him for it, else request for agile coach itself for it.






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "244"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsqa.stackexchange.com%2fquestions%2f38429%2fhow-to-deal-with-or-prevent-idle-in-the-test-team%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      4 Answers
      4






      active

      oldest

      votes








      4 Answers
      4






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      7















      "there is nothing to test"




      That is a strong statement.



      I like to use James Bach's definition of testing:




      Testing is the process of evaluating a product by learning about it
      through exploration and experimentation, which includes to some
      degree: questioning, study, modeling, observation, inference, etc.




      So, unless there is nothing new to learn about the product, yes, you don't have anything to test.



      However, there may be some new things that you can learn. Maybe if you do some of the following, you may uncover them:




      • Pair programming (yes, with the developer);

      • Investigate results of your monitoring and logging instrumentation;

      • Extend your monitoring and logging instrumentation;

      • Create chaos in your environments;

      • Refine backlog to remove duplication and increase simplicity;

      • Watch users (control groups or real ones) using your product;


      • Investigate competitors systems;

      • Refactor any piece of code (production code, automated checking code, deployment code, etc).


      These activities may put a tester in new places, expanding his/hers understanding of the product.






      share|improve this answer
























      • Most of the points have been completely implemented in the past few weeks. We are currently setting up Penetration Testing on a CI basis for our projects. Further education in the team are also on the agenda.

        – Mornon
        9 hours ago
















      7















      "there is nothing to test"




      That is a strong statement.



      I like to use James Bach's definition of testing:




      Testing is the process of evaluating a product by learning about it
      through exploration and experimentation, which includes to some
      degree: questioning, study, modeling, observation, inference, etc.




      So, unless there is nothing new to learn about the product, yes, you don't have anything to test.



      However, there may be some new things that you can learn. Maybe if you do some of the following, you may uncover them:




      • Pair programming (yes, with the developer);

      • Investigate results of your monitoring and logging instrumentation;

      • Extend your monitoring and logging instrumentation;

      • Create chaos in your environments;

      • Refine backlog to remove duplication and increase simplicity;

      • Watch users (control groups or real ones) using your product;


      • Investigate competitors systems;

      • Refactor any piece of code (production code, automated checking code, deployment code, etc).


      These activities may put a tester in new places, expanding his/hers understanding of the product.






      share|improve this answer
























      • Most of the points have been completely implemented in the past few weeks. We are currently setting up Penetration Testing on a CI basis for our projects. Further education in the team are also on the agenda.

        – Mornon
        9 hours ago














      7












      7








      7








      "there is nothing to test"




      That is a strong statement.



      I like to use James Bach's definition of testing:




      Testing is the process of evaluating a product by learning about it
      through exploration and experimentation, which includes to some
      degree: questioning, study, modeling, observation, inference, etc.




      So, unless there is nothing new to learn about the product, yes, you don't have anything to test.



      However, there may be some new things that you can learn. Maybe if you do some of the following, you may uncover them:




      • Pair programming (yes, with the developer);

      • Investigate results of your monitoring and logging instrumentation;

      • Extend your monitoring and logging instrumentation;

      • Create chaos in your environments;

      • Refine backlog to remove duplication and increase simplicity;

      • Watch users (control groups or real ones) using your product;


      • Investigate competitors systems;

      • Refactor any piece of code (production code, automated checking code, deployment code, etc).


      These activities may put a tester in new places, expanding his/hers understanding of the product.






      share|improve this answer














      "there is nothing to test"




      That is a strong statement.



      I like to use James Bach's definition of testing:




      Testing is the process of evaluating a product by learning about it
      through exploration and experimentation, which includes to some
      degree: questioning, study, modeling, observation, inference, etc.




      So, unless there is nothing new to learn about the product, yes, you don't have anything to test.



      However, there may be some new things that you can learn. Maybe if you do some of the following, you may uncover them:




      • Pair programming (yes, with the developer);

      • Investigate results of your monitoring and logging instrumentation;

      • Extend your monitoring and logging instrumentation;

      • Create chaos in your environments;

      • Refine backlog to remove duplication and increase simplicity;

      • Watch users (control groups or real ones) using your product;


      • Investigate competitors systems;

      • Refactor any piece of code (production code, automated checking code, deployment code, etc).


      These activities may put a tester in new places, expanding his/hers understanding of the product.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered 10 hours ago









      João FariasJoão Farias

      3,021415




      3,021415













      • Most of the points have been completely implemented in the past few weeks. We are currently setting up Penetration Testing on a CI basis for our projects. Further education in the team are also on the agenda.

        – Mornon
        9 hours ago



















      • Most of the points have been completely implemented in the past few weeks. We are currently setting up Penetration Testing on a CI basis for our projects. Further education in the team are also on the agenda.

        – Mornon
        9 hours ago

















      Most of the points have been completely implemented in the past few weeks. We are currently setting up Penetration Testing on a CI basis for our projects. Further education in the team are also on the agenda.

      – Mornon
      9 hours ago





      Most of the points have been completely implemented in the past few weeks. We are currently setting up Penetration Testing on a CI basis for our projects. Further education in the team are also on the agenda.

      – Mornon
      9 hours ago











      4














      If you have a set of Regression Tests, testers can start automating them starting with which are easiest to automate. This will save you a lot of time in the long run during Regression Testing. Of course, this requires some programming skills and if the testers do not have those at the moment then this is the great time for them to learn it and apply to automating the tests. This is a win-win for both the testers and the team. As, testers are adding a new skill to their personal tool-set which will eventually benefit the business/company too.






      share|improve this answer
























      • The test automation is up to date, and the CI runs through every day. However, this does not result in enough tasks for the test team. We have also offered training courses and so the testers just trained in Selenium.

        – Mornon
        11 hours ago











      • We are already implementing our CI on Penetration Test, and we are training our testers in terms of safety.

        – Mornon
        11 hours ago











      • @Mornon That's great! Not sure what else can be done. I personally tend to help out on some low priority development tasks.

        – Baljeet Singh
        10 hours ago
















      4














      If you have a set of Regression Tests, testers can start automating them starting with which are easiest to automate. This will save you a lot of time in the long run during Regression Testing. Of course, this requires some programming skills and if the testers do not have those at the moment then this is the great time for them to learn it and apply to automating the tests. This is a win-win for both the testers and the team. As, testers are adding a new skill to their personal tool-set which will eventually benefit the business/company too.






      share|improve this answer
























      • The test automation is up to date, and the CI runs through every day. However, this does not result in enough tasks for the test team. We have also offered training courses and so the testers just trained in Selenium.

        – Mornon
        11 hours ago











      • We are already implementing our CI on Penetration Test, and we are training our testers in terms of safety.

        – Mornon
        11 hours ago











      • @Mornon That's great! Not sure what else can be done. I personally tend to help out on some low priority development tasks.

        – Baljeet Singh
        10 hours ago














      4












      4








      4







      If you have a set of Regression Tests, testers can start automating them starting with which are easiest to automate. This will save you a lot of time in the long run during Regression Testing. Of course, this requires some programming skills and if the testers do not have those at the moment then this is the great time for them to learn it and apply to automating the tests. This is a win-win for both the testers and the team. As, testers are adding a new skill to their personal tool-set which will eventually benefit the business/company too.






      share|improve this answer













      If you have a set of Regression Tests, testers can start automating them starting with which are easiest to automate. This will save you a lot of time in the long run during Regression Testing. Of course, this requires some programming skills and if the testers do not have those at the moment then this is the great time for them to learn it and apply to automating the tests. This is a win-win for both the testers and the team. As, testers are adding a new skill to their personal tool-set which will eventually benefit the business/company too.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered 11 hours ago









      Baljeet SinghBaljeet Singh

      508




      508













      • The test automation is up to date, and the CI runs through every day. However, this does not result in enough tasks for the test team. We have also offered training courses and so the testers just trained in Selenium.

        – Mornon
        11 hours ago











      • We are already implementing our CI on Penetration Test, and we are training our testers in terms of safety.

        – Mornon
        11 hours ago











      • @Mornon That's great! Not sure what else can be done. I personally tend to help out on some low priority development tasks.

        – Baljeet Singh
        10 hours ago



















      • The test automation is up to date, and the CI runs through every day. However, this does not result in enough tasks for the test team. We have also offered training courses and so the testers just trained in Selenium.

        – Mornon
        11 hours ago











      • We are already implementing our CI on Penetration Test, and we are training our testers in terms of safety.

        – Mornon
        11 hours ago











      • @Mornon That's great! Not sure what else can be done. I personally tend to help out on some low priority development tasks.

        – Baljeet Singh
        10 hours ago

















      The test automation is up to date, and the CI runs through every day. However, this does not result in enough tasks for the test team. We have also offered training courses and so the testers just trained in Selenium.

      – Mornon
      11 hours ago





      The test automation is up to date, and the CI runs through every day. However, this does not result in enough tasks for the test team. We have also offered training courses and so the testers just trained in Selenium.

      – Mornon
      11 hours ago













      We are already implementing our CI on Penetration Test, and we are training our testers in terms of safety.

      – Mornon
      11 hours ago





      We are already implementing our CI on Penetration Test, and we are training our testers in terms of safety.

      – Mornon
      11 hours ago













      @Mornon That's great! Not sure what else can be done. I personally tend to help out on some low priority development tasks.

      – Baljeet Singh
      10 hours ago





      @Mornon That's great! Not sure what else can be done. I personally tend to help out on some low priority development tasks.

      – Baljeet Singh
      10 hours ago











      4














      In addition to some of the other suggestions, you could consider a few other options:




      • Build/run load tests for new/recent work (given the maturity of your test automation you may already have this under control)

      • Review existing test automation for obsolete or ineffective tests (You have no idea how much I wish I could reach this point)

      • Review and refactor existing test automation code. In any rapid development environment, automated test code can get dated quite quickly.

      • Review and update older customer documentation. In my experience this can become out of date fairly rapidly if development is quick.

      • Review other documentation to make sure it's up to date. This can include (but is not limited to) use cases, business requirements, database dictionaries, functional requirements, test documentation...

      • Work with product owners to refine any stories in the backlog - or just go in there and review them and ask questions anyway. Testers typically have a unique combination of breadth and depth with a product they're familiar with and can often pick up potentially problematic changes before they go to code.

      • Review the user stories and defects in the current sprint and start planning how to test them. If there's configuration that's needed, it can save a lot of time to set up as much of the configuration as possible before the story/defect is coded.


      A lot of these are things I've done when I found myself in a holding pattern.






      share|improve this answer




























        4














        In addition to some of the other suggestions, you could consider a few other options:




        • Build/run load tests for new/recent work (given the maturity of your test automation you may already have this under control)

        • Review existing test automation for obsolete or ineffective tests (You have no idea how much I wish I could reach this point)

        • Review and refactor existing test automation code. In any rapid development environment, automated test code can get dated quite quickly.

        • Review and update older customer documentation. In my experience this can become out of date fairly rapidly if development is quick.

        • Review other documentation to make sure it's up to date. This can include (but is not limited to) use cases, business requirements, database dictionaries, functional requirements, test documentation...

        • Work with product owners to refine any stories in the backlog - or just go in there and review them and ask questions anyway. Testers typically have a unique combination of breadth and depth with a product they're familiar with and can often pick up potentially problematic changes before they go to code.

        • Review the user stories and defects in the current sprint and start planning how to test them. If there's configuration that's needed, it can save a lot of time to set up as much of the configuration as possible before the story/defect is coded.


        A lot of these are things I've done when I found myself in a holding pattern.






        share|improve this answer


























          4












          4








          4







          In addition to some of the other suggestions, you could consider a few other options:




          • Build/run load tests for new/recent work (given the maturity of your test automation you may already have this under control)

          • Review existing test automation for obsolete or ineffective tests (You have no idea how much I wish I could reach this point)

          • Review and refactor existing test automation code. In any rapid development environment, automated test code can get dated quite quickly.

          • Review and update older customer documentation. In my experience this can become out of date fairly rapidly if development is quick.

          • Review other documentation to make sure it's up to date. This can include (but is not limited to) use cases, business requirements, database dictionaries, functional requirements, test documentation...

          • Work with product owners to refine any stories in the backlog - or just go in there and review them and ask questions anyway. Testers typically have a unique combination of breadth and depth with a product they're familiar with and can often pick up potentially problematic changes before they go to code.

          • Review the user stories and defects in the current sprint and start planning how to test them. If there's configuration that's needed, it can save a lot of time to set up as much of the configuration as possible before the story/defect is coded.


          A lot of these are things I've done when I found myself in a holding pattern.






          share|improve this answer













          In addition to some of the other suggestions, you could consider a few other options:




          • Build/run load tests for new/recent work (given the maturity of your test automation you may already have this under control)

          • Review existing test automation for obsolete or ineffective tests (You have no idea how much I wish I could reach this point)

          • Review and refactor existing test automation code. In any rapid development environment, automated test code can get dated quite quickly.

          • Review and update older customer documentation. In my experience this can become out of date fairly rapidly if development is quick.

          • Review other documentation to make sure it's up to date. This can include (but is not limited to) use cases, business requirements, database dictionaries, functional requirements, test documentation...

          • Work with product owners to refine any stories in the backlog - or just go in there and review them and ask questions anyway. Testers typically have a unique combination of breadth and depth with a product they're familiar with and can often pick up potentially problematic changes before they go to code.

          • Review the user stories and defects in the current sprint and start planning how to test them. If there's configuration that's needed, it can save a lot of time to set up as much of the configuration as possible before the story/defect is coded.


          A lot of these are things I've done when I found myself in a holding pattern.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 9 hours ago









          Kate PaulkKate Paulk

          24.9k64085




          24.9k64085























              1














              Since you mentioned, it's a scrum.. its actually the scrum master role to make a deliverable level module to prepare from tiny user stories, so that tester can start preparing their test case based on the deliverable level.



              Say for example, if a micro service which cannot be tested, it should not be included alone in the sprint, rather connecting module (frontend or api) should be included.speak to your scrum master, ask him for it, else request for agile coach itself for it.






              share|improve this answer




























                1














                Since you mentioned, it's a scrum.. its actually the scrum master role to make a deliverable level module to prepare from tiny user stories, so that tester can start preparing their test case based on the deliverable level.



                Say for example, if a micro service which cannot be tested, it should not be included alone in the sprint, rather connecting module (frontend or api) should be included.speak to your scrum master, ask him for it, else request for agile coach itself for it.






                share|improve this answer


























                  1












                  1








                  1







                  Since you mentioned, it's a scrum.. its actually the scrum master role to make a deliverable level module to prepare from tiny user stories, so that tester can start preparing their test case based on the deliverable level.



                  Say for example, if a micro service which cannot be tested, it should not be included alone in the sprint, rather connecting module (frontend or api) should be included.speak to your scrum master, ask him for it, else request for agile coach itself for it.






                  share|improve this answer













                  Since you mentioned, it's a scrum.. its actually the scrum master role to make a deliverable level module to prepare from tiny user stories, so that tester can start preparing their test case based on the deliverable level.



                  Say for example, if a micro service which cannot be tested, it should not be included alone in the sprint, rather connecting module (frontend or api) should be included.speak to your scrum master, ask him for it, else request for agile coach itself for it.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 9 hours ago









                  ManuManu

                  648




                  648






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Software Quality Assurance & Testing Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsqa.stackexchange.com%2fquestions%2f38429%2fhow-to-deal-with-or-prevent-idle-in-the-test-team%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      How to make a Squid Proxy server?

                      Is this a new Fibonacci Identity?

                      19世紀