Chronicles Of Testing

Test coverage while exploratory testing needn't be limited to one or more of the below factors: -Test ideas matching the requirements -Test ideas matching a tester’s skills Let us explore the other options to provide test coverage when: -The requirements are not yet available or are incomplete, which usually is the case in an agile way of working with frequent changes being made to the product. -There is not yet a certain way to map the requirements with the test ideas generated. -When a tester does not know, if the test coverage provided is enough / sufficient to the ask of the product owner / business. Many may differ by the mention of enough / sufficient coverage by ruling out with an answer that the test cases match the requirements. In such a case, have you as a tester ever been questioned: “Why was this not tested?” And what was your answer? The answer, “I have provided test coverage as per the requirements gathered” help you get away from answering...

Traditionally, software testing was the study of requirements, preparation of tests, execution of the identified tests in a controlled environment and presenting the results to the sources who should have access to this information. Then  came the want to universalize, generalize, process, package and sell this traditional approach. The same was sold by company X and bought by company Y. The word spread and companies A, B and C bought it too because company Y’s testimonials were grand. Caution: Be aware of who you talk and listen to in the business world. In the early days of software testing, the limitations set by the traditional approach and the decline of this approach did not go unnoticed. With the lack of awareness, that the traditional approach to software testing is just not sufficient to deliver quality, companies A, B, C and Y stayed back to relish the thriving business and failed to embrace the change that was happening as early as in the 1980’s. This decl...

As I continue my journey towards brainual testing. Here's a snippet on exploratory testing. I choose to frame this article as a Q & A session as I learnt it from Carsten Feilberg, I thank him for sharing his knowledge. Connect with Carsten here . SBTM - Session Based Test Management - is a scheme for managing testing by dividing the testing into chunks of time, called sessions. What is Session Log? Session Log - the log of the testing carried out in a session of Exploratory Testing. Where does this term Session Log stem from? The term session comes from session-based testing. Is there a minimum and maximum time for session based testing? Session based testing could be x minutes of uninterrupted time, which is devoted in testing a set mission. The tester can set the max and min time. Does 3-4 testers together doing testing for a set time qualify for SBTM? Not necessarily SBTM, but the app...