1

I am working in a agile testing project. I am new in testing field, please help me if somebody knows the answer.

My questions are,

  1. Are test cases needed in agile testing or do we directly write automation scripts?

  2. If our team did development and push it to testing, what should be my first approach? Should I directly write automation scripts?

I don't like to do monkey testing.

Please help me to clarify my doubts.

2

My thoughts

Are test cases needed in agile testing or do we directly write automation scripts?

I would strongly recommend you write test cases first and then do a feasibility study of which tests should be automated after discussion with stakeholders.

If our team did development and push it to testing, what should be my first approach? Should I directly write automation scripts?

For the initial builds, you should first do a round of smoke testing and then look at which scenarios/tests need to be automated

  • @BountyHaunter Smoke testing we are doing manually.. right ? Write test cases for smoke testing..Smoke testing means to verify that the critical functionalities of the system is working fine. – user21268 Nov 22 '16 at 6:35
  • That is correct, Smoke testing has to be done manually. This will ensure that most important features/functions work, and determine if the build is stable enough to start automation – BountyHunter Nov 22 '16 at 6:54
  • ..Hai manually means monkey testing right ? – user21268 Nov 22 '16 at 6:58
  • 1
    Monkey testing is more of Exploratory testing where you test the application or system by providing random inputs and checking the behavior – BountyHunter Nov 22 '16 at 7:07
  • ok got it.. After testing smoke then can go to sanity, then finally regression, then we need to automate the each test cases right ? – user21268 Nov 22 '16 at 7:30
1

In agile projects every sprint timeline we have:

  • new functionality to be tested (the size of this part is nearly the same every sprint)
  • regression & verification of bug fixes (and this part becomes bigger from sprint to sprint)

New functionality

No automation, More informal scripted tests (test cases), Less Exploratory testing

Commonly testing in agile is started when new code arrives, but in this case testing loses precious time. Ideally tester should participate in scrum meetings to have full understanding of user stories, so he could represent end user interests. This early phase gives you sketches of test cases.

Then as software arrives you check it with this informal test cases (extending them according to your new knowledge of the software). This is the first phase of testing, scripted manual testing (there should not be too much exploration) to check basic functions of software. This is how you test new functionality.

Regression & verification

More automated tests, Less scripted tests (test cases), and Exploratory testing as a separate part of testing process

As soon as core functionality becomes stable (business process or part of it could be accomplished) you should start with automation. Core business functionality should be validated with automated tests. This will save you time on regression & verification to do exploratory testing without scripted test cases but with great mind efforts. Be sure Exploratory testing is nearly useless if the basic features are not working.

P.S.: please do not mix Exploratory testing with Monkey testing. The first is about emphasizing the dominant thought process involved in unscripted testing, but second one is about random input to the tested system. Professional tester should not do monkey testing (there is an exception: randomization of automated tests, but generally this is not monkey testing)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy