What are people’s favorite methods to organize test cases? Is there any Acumatica-specific way to organize test cases?
I would like to ensure users fully test new reports, processes, or preference settings before going live with changes.
Do you use a Word doc or Excel sheet? Is there a software system that works well?
Best answer by Laura02
View original
Hi
Alternatively, you can also use, Acumatica's Wiki feature to document test cases, creating custom fields in Acumatica to track test case details, or utilizing Acumatica's integrated project management capabilities to manage testing tasks.
Let me know which works well for your team?
Good luck!
Shweta
+18
Hello,
I think your question is more about what documentation works well, but the answer lies more in getting to know the humans who are doing the testing. (I agree with the previous poster - do the testers have time to work on their own, and how many details do they need?)
With some clients, I can ask them to select a few examples from regular daily work using the new methods, new workflow, and new reports.
With other clients, I meet them and step through the process of testing a few examples from regular daily work and we try out new procedures and new reports together.
In both cases I keep testing steps brief - for example, “Enter and release a Bill.” (Not field by field instructions → field by field should not be needed; test subjects should be the strongest users of the group.)
When a client indicates they can test on their own versus another meeting…
Laura
I would suggest for better visibility go for Document management systems such as SharePoint or Google drive to organize test cases in Word documents or other file formats. These systems offer version control, collaboration features, and document sharing capabilities.
With other clients, I meet them and step through the process of testing a few examples from regular daily work and we try out new procedures and new reports together.
In both cases I keep testing steps brief - for example, “Enter and release a Bill.” (Not field by field instructions → field by field should not be needed; test subjects should be the strongest users of the group.)
I like your point that the instructions don’t need to be field by field as the end user knows well enough. That definitely brings down the intimidation level.
Great points on how to keep them accountable, definitely going to use many of those tactics!
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.