Tagged Questions

Test documentation describes the artifacts created before, during, and after testing for the purpose of communicating with stakeholders to solicit feedback, to capture your intended approach to provide guidance for your team, to provide actionable information for business decision makers, and to ...

We are integrating with an out sourcing team to start automating our regular test cases
What is the best type of documents to explain our scenarios to the other team?
we want to explain to them how ...

I tried used apigen for generate documentation from netbeans i followed all steps from page but when i do this i found a file.txt with things that i do not understand.
I did not find a file.html with ...

In a test case, what qualifies as an input? Must it be what the tester types as input with their keyboard?
IEEE 829-2008 only lists values, constants, transaction files, and their storage locations ...

It seems relatively easy to find bug tracking tools, but I'm looking for a way to document the process of fixing the defects that will track things such as: who is working on it, being sure that it ...

Background: Combining separate Test Procedure and Test Case documentation has advantages, but so does leaving them separate. IEEE std. 829 mentions system level of complexity as a contributing factor ...

The automation code I'm working with was written by several people before me. It's messy, complex, etc. There are barely any comments within the code. It takes me an extremely long time to figure out ...

I haven't found many resources where people show-and-tell the quality and testing-related projects they're working on. I don't see the same drive to innovate in the SQA community as I do in others. Is ...

I am preparing documentation on a software product for my company.
Can anyone provide me suggestions for preparing a better document will help me a lot.
Are screenshots necessary while preparing the ...

I'm in the process of updating document templates for a customer. Part of the documentation template stack are the usual QA items: Requirements (RS), Architecture (ADD), Test Plan (TP) and Test Report ...

I'm getting ready to release the next version of our software. In the past when the release is ready to go I will send around an email saying "release xxx is done" and include a basic set of release ...

I've just wrote an UAT script specifying all of the use cases step by step (quite standard).
However the customer is asking us for a UAT protocol and we have no clue on what he means by that. Anyone ...

Can anyone recommend some software that can be used to document the results of functional software testing?
This is not at developer level, it is for testers to follow documented procedures/scripts ...

We follow a BDD approach to development, we have our testers creating scenarios from a specification, and these are then given to our developers before any work is started. However, we find that some ...

What are the main points that should be included in a test strategy document for a particular project? I'm not looking at details but more from a high level overview.
I would like to make it a brief ...

I've been in many difference sized companies and in many different environments where we've used terms interchangably, Testing Terms, Development Terms and Process types have been overloaded in one ...