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












5















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
    17 hours ago











  • yes, all developers and all testers are fully involved in the project

    – Mornon
    14 hours ago
















5















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
    17 hours ago











  • yes, all developers and all testers are fully involved in the project

    – Mornon
    14 hours ago














5












5








5


2






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 yesterday









MornonMornon

1249




1249













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

    – user3067860
    17 hours ago











  • yes, all developers and all testers are fully involved in the project

    – Mornon
    14 hours ago



















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

    – user3067860
    17 hours ago











  • yes, all developers and all testers are fully involved in the project

    – Mornon
    14 hours ago

















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

– user3067860
17 hours ago





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

– user3067860
17 hours ago













yes, all developers and all testers are fully involved in the project

– Mornon
14 hours ago





yes, all developers and all testers are fully involved in the project

– Mornon
14 hours ago










4 Answers
4






active

oldest

votes


















14















"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
    yesterday



















7














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














    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
      yesterday











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

      – Mornon
      yesterday











    • @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
      yesterday



















    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









      14















      "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
        yesterday
















      14















      "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
        yesterday














      14












      14








      14








      "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 yesterday









      João FariasJoão Farias

      3,091416




      3,091416













      • 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
        yesterday



















      • 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
        yesterday

















      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
      yesterday





      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
      yesterday











      7














      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




























        7














        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


























          7












          7








          7







          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 yesterday









          Kate PaulkKate Paulk

          24.9k64085




          24.9k64085























              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
                yesterday











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

                – Mornon
                yesterday











              • @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
                yesterday
















              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
                yesterday











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

                – Mornon
                yesterday











              • @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
                yesterday














              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 yesterday









              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
                yesterday











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

                – Mornon
                yesterday











              • @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
                yesterday



















              • 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
                yesterday











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

                – Mornon
                yesterday











              • @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
                yesterday

















              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
              yesterday





              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
              yesterday













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

              – Mornon
              yesterday





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

              – Mornon
              yesterday













              @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
              yesterday





              @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
              yesterday











              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 yesterday









                  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

                      Færeyskur hestur Heimild | Tengill | Tilvísanir | LeiðsagnarvalRossið - síða um færeyska hrossið á færeyskuGott ár hjá færeyska hestinum

                      He _____ here since 1970 . Answer needed [closed]What does “since he was so high” mean?Meaning of “catch birds for”?How do I ensure “since” takes the meaning I want?“Who cares here” meaningWhat does “right round toward” mean?the time tense (had now been detected)What does the phrase “ring around the roses” mean here?Correct usage of “visited upon”Meaning of “foiled rail sabotage bid”It was the third time I had gone to Rome or It is the third time I had been to Rome

                      Slayer Innehåll Historia | Stil, komposition och lyrik | Bandets betydelse och framgångar | Sidoprojekt och samarbeten | Kontroverser | Medlemmar | Utmärkelser och nomineringar | Turnéer och festivaler | Diskografi | Referenser | Externa länkar | Navigeringsmenywww.slayer.net”Metal Massacre vol. 1””Metal Massacre vol. 3””Metal Massacre Volume III””Show No Mercy””Haunting the Chapel””Live Undead””Hell Awaits””Reign in Blood””Reign in Blood””Gold & Platinum – Reign in Blood””Golden Gods Awards Winners”originalet”Kerrang! Hall Of Fame””Slayer Looks Back On 37-Year Career In New Video Series: Part Two””South of Heaven””Gold & Platinum – South of Heaven””Seasons in the Abyss””Gold & Platinum - Seasons in the Abyss””Divine Intervention””Divine Intervention - Release group by Slayer””Gold & Platinum - Divine Intervention””Live Intrusion””Undisputed Attitude””Abolish Government/Superficial Love””Release “Slatanic Slaughter: A Tribute to Slayer” by Various Artists””Diabolus in Musica””Soundtrack to the Apocalypse””God Hates Us All””Systematic - Relationships””War at the Warfield””Gold & Platinum - War at the Warfield””Soundtrack to the Apocalypse””Gold & Platinum - Still Reigning””Metallica, Slayer, Iron Mauden Among Winners At Metal Hammer Awards””Eternal Pyre””Eternal Pyre - Slayer release group””Eternal Pyre””Metal Storm Awards 2006””Kerrang! Hall Of Fame””Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Bullet-For My Valentine booed at Metal Hammer Golden Gods Awards””Unholy Aliance””The End Of Slayer?””Slayer: We Could Thrash Out Two More Albums If We're Fast Enough...””'The Unholy Alliance: Chapter III' UK Dates Added”originalet”Megadeth And Slayer To Co-Headline 'Canadian Carnage' Trek”originalet”World Painted Blood””Release “World Painted Blood” by Slayer””Metallica Heading To Cinemas””Slayer, Megadeth To Join Forces For 'European Carnage' Tour - Dec. 18, 2010”originalet”Slayer's Hanneman Contracts Acute Infection; Band To Bring In Guest Guitarist””Cannibal Corpse's Pat O'Brien Will Step In As Slayer's Guest Guitarist”originalet”Slayer’s Jeff Hanneman Dead at 49””Dave Lombardo Says He Made Only $67,000 In 2011 While Touring With Slayer””Slayer: We Do Not Agree With Dave Lombardo's Substance Or Timeline Of Events””Slayer Welcomes Drummer Paul Bostaph Back To The Fold””Slayer Hope to Unveil Never-Before-Heard Jeff Hanneman Material on Next Album””Slayer Debut New Song 'Implode' During Surprise Golden Gods Appearance””Release group Repentless by Slayer””Repentless - Slayer - Credits””Slayer””Metal Storm Awards 2015””Slayer - to release comic book "Repentless #1"””Slayer To Release 'Repentless' 6.66" Vinyl Box Set””BREAKING NEWS: Slayer Announce Farewell Tour””Slayer Recruit Lamb of God, Anthrax, Behemoth + Testament for Final Tour””Slayer lägger ner efter 37 år””Slayer Announces Second North American Leg Of 'Final' Tour””Final World Tour””Slayer Announces Final European Tour With Lamb of God, Anthrax And Obituary””Slayer To Tour Europe With Lamb of God, Anthrax And Obituary””Slayer To Play 'Last French Show Ever' At Next Year's Hellfst””Slayer's Final World Tour Will Extend Into 2019””Death Angel's Rob Cavestany On Slayer's 'Farewell' Tour: 'Some Of Us Could See This Coming'””Testament Has No Plans To Retire Anytime Soon, Says Chuck Billy””Anthrax's Scott Ian On Slayer's 'Farewell' Tour Plans: 'I Was Surprised And I Wasn't Surprised'””Slayer””Slayer's Morbid Schlock””Review/Rock; For Slayer, the Mania Is the Message””Slayer - Biography””Slayer - Reign In Blood”originalet”Dave Lombardo””An exclusive oral history of Slayer”originalet”Exclusive! Interview With Slayer Guitarist Jeff Hanneman”originalet”Thinking Out Loud: Slayer's Kerry King on hair metal, Satan and being polite””Slayer Lyrics””Slayer - Biography””Most influential artists for extreme metal music””Slayer - Reign in Blood””Slayer guitarist Jeff Hanneman dies aged 49””Slatanic Slaughter: A Tribute to Slayer””Gateway to Hell: A Tribute to Slayer””Covered In Blood””Slayer: The Origins of Thrash in San Francisco, CA.””Why They Rule - #6 Slayer”originalet”Guitar World's 100 Greatest Heavy Metal Guitarists Of All Time”originalet”The fans have spoken: Slayer comes out on top in readers' polls”originalet”Tribute to Jeff Hanneman (1964-2013)””Lamb Of God Frontman: We Sound Like A Slayer Rip-Off””BEHEMOTH Frontman Pays Tribute To SLAYER's JEFF HANNEMAN””Slayer, Hatebreed Doing Double Duty On This Year's Ozzfest””System of a Down””Lacuna Coil’s Andrea Ferro Talks Influences, Skateboarding, Band Origins + More””Slayer - Reign in Blood””Into The Lungs of Hell””Slayer rules - en utställning om fans””Slayer and Their Fans Slashed Through a No-Holds-Barred Night at Gas Monkey””Home””Slayer””Gold & Platinum - The Big 4 Live from Sofia, Bulgaria””Exclusive! Interview With Slayer Guitarist Kerry King””2008-02-23: Wiltern, Los Angeles, CA, USA””Slayer's Kerry King To Perform With Megadeth Tonight! - Oct. 21, 2010”originalet”Dave Lombardo - Biography”Slayer Case DismissedArkiveradUltimate Classic Rock: Slayer guitarist Jeff Hanneman dead at 49.”Slayer: "We could never do any thing like Some Kind Of Monster..."””Cannibal Corpse'S Pat O'Brien Will Step In As Slayer'S Guest Guitarist | The Official Slayer Site”originalet”Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Kerrang! Awards 2006 Blog: Kerrang! Hall Of Fame””Kerrang! Awards 2013: Kerrang! Legend”originalet”Metallica, Slayer, Iron Maien Among Winners At Metal Hammer Awards””Metal Hammer Golden Gods Awards””Bullet For My Valentine Booed At Metal Hammer Golden Gods Awards””Metal Storm Awards 2006””Metal Storm Awards 2015””Slayer's Concert History””Slayer - Relationships””Slayer - Releases”Slayers officiella webbplatsSlayer på MusicBrainzOfficiell webbplatsSlayerSlayerr1373445760000 0001 1540 47353068615-5086262726cb13906545x(data)6033143kn20030215029