When testing large stories with limited time, efficiency becomes crucial. What tools or techniques do you rely on to streamline the testing process? How do these tools help you prioritize critical paths, automate repetitive tasks, and manage test coverage quickly? Additionally, what methods do you use to ensure that testing is thorough despite the time constraints?
What tools or techniques can you use to test large stories more efficiently in a short period?
+5
+1- Telling the project management that testing is very limited, which is a risk on its own, and asking for their priorities (which I always do, time is always limited. Sometimes more sometimes less).
- Discuss with the team / important stakeholders what is crucial for the feature.
- Giving regular updates on the state of testing so that management is well informed for decisions.
- Developing my own test tools (not just test case execution automation), tailored to the needs of testing
- e.g. I have developed a tool which reads data from different data bases (including configurable conversion of data) and compares it. This includes a compare report in a data base which I can easily filter for different cases.
We can stop testing at any time, but we could go on for nearly ever. Management should tell us what they need to know to make business decisions.
+5Sebastian Stautz wrote:
- Telling the project management that testing is very limited, which is a risk on its own, and asking for their priorities (which I always do, time is always limited. Sometimes more sometimes less).
- Discuss with the team / important stakeholders what is crucial for the feature.
- Giving regular updates on the state of testing so that management is well informed for decisions.
- Developing my own test tools (not just test case execution automation), tailored to the needs of testing
- e.g. I have developed a tool which reads data from different data bases (including configurable conversion of data) and compares it. This includes a compare report in a data base which I can easily filter for different cases.
We can stop testing at any time, but we could go on for nearly ever. Management should tell us what they need to know to make business decisions.
Hi
Could you share the tool documentation which is you developed or is this any demo video available?
+1I fear this neither not that easily. The tools is no available in public and I haven’t yet discussed to put it into public. Nor is the documentation very fledged out.
But I guess can give you screenshots at which I removed confidential information.
How to configure exporting from data base into csv files:
How to configure the data comparison:
And this is an excerpt of main table of the comparison report. I go through this, making use of filters, to identify problems (not all differences are errors, some are explainable) and finding patterns to identify deeper causes.
Reply
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.