Forum Discussion
Monkeys and Robots usually. Sometimes we just think of something that needs to be automated and a script appears. Sometimes a more advanced civilization from the stars will visit us and automate our processes.
Seriously though QA does this at my current and former places of employment.
At former job my wife was involved with generating scripts, and still is. (she has no programming experience)
I created the framework there that she uses it to this day.
My current job I wrote the initial framework and other QA assist with updating it as needed (all QA here have OOP experience).
Primarily they are focused on created scripts.
Much like all projects it's important to recognize the individual strengths of your team members if you want to succeed.
I say this because many times it is overlooked.
For example:
I enjoy designing the framework, writing code, and maintaining that code.
I do not enjoy writing excel spreadsheets, populating data, etc..
My wife enjoys writing excel spreadsheets, populating data, etc..
My wife hates writing code, learning code, and designing processes or framework.
We could fight all day long every day about who should be involved in what, but instead it has worked very well to simply allow people to do what they are good at, and what they are interested in.
In my current position I have been working to engage developers in our automated QA, but I also recognize that it is not something they are overly interested in. And that's OK for me. I simply need them to have realistic expectations and ideas about what can and cannot be automated; For them to be available when a solution is required at the application level and not within Test Complete.
- Marsha_R8 years agoChampion Level 3
Our developers write the unit tests for their own tests and the QAs review them. QAs do the other automated testing.
Related Content
- 5 years agoMr-Shlomi
- 7 months agomengbinhao
- 3 years agombeckham
- 4 years agoJosh_147
Recent Discussions
- 10 hours agoSvetaG