qa - Difference between Quality Assurance and Software Testing -

What are the differences between the software testing group and the Quality Assurance Team? Do they mention the same? If not, then what is the work of each of these two teams?

Both are the same ...

for pre; Our company performs a full test of the applications we have made in the QA team. They ensure that all applications are working as expected (SAT System Acceptance Test).

Software testing group (also QA) but from our customer. They will hold UAT (User Acceptance Test).

USR (URS) - User System Requirements (User Requirements Specification) I think this is the only thing - I have come too much in the latter expression. It should be a document that explains what the user (customer) wants from the system. How it's not working, but what's going to be doing "I want a machine to make coffee, and it should have an option for white, black, espresso and chicken soup Oh and sugar Oh, and in it There will be two different shaped cups and one biscuit machine. " Etc. are included. This should be signed between the initial supplier and the customer to be measured at the end of an agreed set of deliverables. (Two different types of cups are not a good example, they should be specified in liquid ounces, milliliters, this is a specification document, not just details.)

FDS - Functional Design Specification here is changing the requirements ('what') in the supplier methods ('how'). This document defines for him how he wants to fulfill the URL. At the same time, and following the URS, some test specification should start to emerge. How can we say that it is working fine? What will be the agreed steps?

FAT - Factory Approval Test Once a machine / system / software has been collected in the supplier's factory, a formal test should be done with checkpoints and performance measures to prove that it meets the URL Is able to. NB does not mean that it will meet the URS there and there after that. This can be impossible until it is abolished at the end of the site. Often customers will request to be present at FAT to see before allowing them to be sent to their site. Some projects will have to pay the stage on successful completion of a witness FAT.

UAT - Ready to install and run in user's premises with user acceptance test tool. It is necessary to prove that it can all agree in the URS. Like Doug said, this is where the user satisfies himself that the system is largely as requested and accept the delivery of the equipment. Since then, it becomes an invoice for the system. Further work can be continued by the supplier, but changing it should be agreed and defined for the original imagery in notice or deviation, and I hope that most of this will represent additional charges.