Skip to main content

Testing in Sessions..

When all of us were studying at school or college (and even now) we have periods of 45 minutes or 60 minutes in length. Have you ever thought why this is limited to 60 minutes or 45 minutes? The answer is simple students will loose concentration after 45 minutes. Testers are like students and they will loose concentration after a certain amount of time. When you are testing an application make sure that you take a break after 45 minutes and then come back with a fresh mind to resume testing. When you are writing test cases ensure that the test cases does not contain too many steps. If your test case is lengthy it may take hours or days to execute. I have seen testers writing test cases with 400 or 500 steps which may take more than a day to execute.
The tester may start the execution of the test cases may be with Build 1 and by the time he reaches 50% of the execution you may have Build 2 from the development. You may be forced to start the test case execution from Step 1 again if the feature or requirements under test underwent a change in Build 2. It will be a good practice to limit the number of steps in your test case to 20 or 25 steps so that you can complete the test case execution in less than an hour's time. It may be not be possible to limit the number of steps in test cases for example when you are testing a complete end to end flow of an application. So try to execute test cases or perform adhoc testing in sessions of shorter duration and find as many defects as possible.

Comments

Popular posts from this blog

Quantum Computing Trends

With the advancements in technology, we shifted from traditional computers to its digital version, which included zero’s and one’s and now, to the latest and fastest upgraded computers i.e. Quantum Computers. Built on the pioneering ideas of physicists Richard Feynman and David Deutsch in the 1980s, Quantum Computers leverage the unique properties of matter at nanoscale. Quantum computing uses quantum physics to solve the problems which today’s computers can never tackle. There are two characteristics of quantum computer which make them the computers of the future. First, quantum computing is built on qubits that can be overlays of zero and one i.e. half part of a zero and a half part of a one at the same time. Second, qubits become entangled and exist in groups. Because of its capability to solve problems, high speed and accuracy, quantum computing has immediate applications in fields like pharmaceutical, cryptography, machine learning and search. Realizing the pot...

TDD BDD and SDET REsume

 **TDD vs BDD** Test-Driven Development (TDD) and Behavior-Driven Development (BDD) are both agile methodologies but with distinct focuses and processes. TDD vs BDD a developer-centric practice, emphasizes writing tests before the actual code, guiding software development through small, testable chunks. It's particularly effective in ensuring that the codebase remains bug-free and maintainable. BDD, on the other hand, extends TDD by specifying software behaviors using a language understandable by all stakeholders, including non-technical ones. This approach fosters collaboration and a shared understanding of the project's goals, making it easier to align development with customer needs and expectations. While TDD is focused on the technical aspects and validation of software functionality, BDD is more about clear communication and the behavior of the application from the user's perspective. **SDET Resume** An SDET Resume should effectively showcase a blend of software dev...

7 Software Testing Books Worth Reading!