Key learnings
While working as a tester, Miguel has always tried to get as involved in projects as much as possible. He enjoyed collaborating across teams and different countries and continuously got excellent feedback from his superiors.
While trying to be as precise as possible as a tester, Miguel got used to deconstruct each task he was given into its elements in order to draft a plan for improving it. This made his work approach easy to execute and accurate.
During his involvement in UAT, Miguel has taken a lot of time to understand the systems behind the Just Ask system, which grow in complexity.
Risks identified
Out from all his attention to detail, Miguel has found a few risks involving the developing of testing cycles for JustAsk. With a system growing in complexity, the usual scripting process is not as ideal as it should since it leaves some room for mistakes that we can easily avoid.
The main issues spotted have been the following:
-Different naming conventions
-Scripting with ambiguous information
-Over scripting
-Uploading bugs
Suggested approach
-Systematic identification of main focus of testing
-Standarization of test elements
-Use of Excel rules to avoid inconsistencies
All of this is summed up in a pilot called "Dragon Scripting Standard" in reference to how the scales of a dragon support each other. It is meant to be a system easy to implement in UAT that will eliminate the majority of the bugs that have been named above, allowing the UAT lead to have all the atention in controlling the process.