In our test practice, we are facing the problem to save test case doc in one place and test code another place. In a long run, how to keep them synchronized is a problem. Any idea to do so?
Do you have any thoughts regarding software quality assurance and certifications? Are there industry standards for software QA or any certs that will help a person advance in the field?
Minglei, one thought is to keep the test docs with the test code under source control. Let's say in the form of javadoc where functions = test cases and classes = test suites. That way, docs can be auto-generated on commits.
The first year I worked after University at Ericsson the number of offices seats was short so I got a place right beside the QA for the project.
That tend to give you a view on system development that gives a rather big priority on defence programming.
It affects you coming straight from the university sitting beside some old - well not bitter - but experianced tester who goes through code he often feels lack any quality at all.
In our test practice, we are facing the problem to save test case doc in one place and test code another place. In a long run, how to keep them synchronized is a problem. Any idea to do so?
ResponderEliminarDo you have any thoughts regarding software quality assurance and certifications? Are there industry standards for software QA or any certs that will help a person advance in the field?
ResponderEliminarMinglei, one thought is to keep the test docs with the test code under source control. Let's say in the form of javadoc where functions = test cases and classes = test suites. That way, docs can be auto-generated on commits.
ResponderEliminarJames,
ResponderEliminarThanks for 2 great posts.
What about that part of you which is test team specific - the administration, motivational stuff, the mentoring bit etc.
And the other bit which keeps your bosses content and silent or at bay... via reports with pretty graphs..
And what about retrospectives and so on.
The first year I worked after University at Ericsson the number of offices seats was short so I got a place right beside the QA for the project.
ResponderEliminarThat tend to give you a view on system development that gives a rather big priority on defence programming.
It affects you coming straight from the university sitting beside some old - well not bitter - but experianced tester who goes through code he often feels lack any quality at all.