Hi, I'm looking for next info:
What document types could be used when describing software testing automation (on any phase, automation planning, test design, implementation, reporting)? Is there any standard types of documents? If someone could provide any examples and templates for different types of documents? What is the difference between manual testing documentation and automated?
What types of documents are used in your team?
I'll be grateful for any of this information.
I'd be interested to see what others out there are doing. I've worked for a company that basically uses a free form wiki to track which test cases are automated. What they did was in a wiki document, list the functional areas, what needed to be tested, and list the automated test cases that cover those areas.
The company I'm currently working in is just getting it's efforts started. We plan on using our Scrum tool (Version One) to track the tests. In a different team in the same company, they are using Quality Center for everything, but have some excel and mind map files for defining the test scenarios.
I feel that its somehow important,Basically all depends on how something can work in a good way according to you guys.Documentation has to be done because that is what makes it looks reasonable and the same time good with the outcomes.
I take the manual test case documentation and use that to automate. I'm responsible for updating the test cases from that point forward. As far as automation documentation, I'm putting together training documents.
Patience is like bread I say.... I ran out of that yesterday.
I've started a new company. I recently setup a system where we are using a TCM system to manage everything. I wrote some special decorators into the test framework where I can add decorators (they call them attributes in C#) where I tags tests like "[TC404]", Then every time the test is run automated, it'll report back and add a test result entry into the TCM system. Then what's left to manual test is all the left over tests.