Re: UAT vs QA
These are definitions from Wikiperid - from reading these you should be able to come up with differences. These are just common sense definitions. UAT and QC is basically the same but somewhat different depending on your company set-up and requirements. If you are planning for an interview your knowledge may need to be more comprehensive and detailed that you can get from this.
"User Acceptance Testing (UAT) is a process to obtain confirmation by a Subject Matter Expert (SME), preferably the owner or client of the object under test, through trial or review, that the modification or addition meets mutually agreed-upon requirements. In software development, UAT is one of the final stages of a project and will often occur before a client or customer accepts a new system.
Users of the system will perform these tests which, ideally, developers have derived from the client's contract or the user requirements specification.
Test designers will draw up formal tests and devise a range of severity levels. The test designer may or may not be the creator of the formal test cases for the same system. The focus is on a final verification of the required business function and flow of the system, emulating real-world usage of the system. The idea is that if the software works as intended and without issues during a simulation of normal use, it will work just the same in production. These tests are not focused on fleshing out simple problems (spelling mistakes, cosmetic problems) or show stoppers (major problems like the software crashing, software will not run etc.). Developers should have worked out these issues during unit testing and integration testing.
The results of these tests will give confidence to the customers of how the system will perform in production. "
QA (QC) testing
"Software testing is the process used to help identify the correctness, completeness, security and quality of developed computer software.Testing is a process of executing a program or application in the intent of finding errors. With that in mind, testing can never completely establish the correctness of arbitrary computer software. In other words, testing is criticism or comparison, that is comparing the actual value with an expected one. I like ice-cream There are many approaches to software testing, but effective testing of complex products is essentially a process of investigation, not merely a matter of creating and following rote procedure. One definition of testing is "the process of questioning a product in order to evaluate it", where the "questions" are things the tester tries to do with the product, and the product answers with its behavior in reaction to the probing of the tester. Although most of the intellectual processes of testing are nearly identical to that of review or inspection, the word testing is connoted to mean the dynamic analysis of the product—putting the product through its paces. The quality of the application can, and normally does, vary widely from system to system but some of the common quality attributes include reliability, stability, portability, maintainability and usability.A good test is the one which finds an as yet undiscovered error. Refer to the ISO standard ISO 9126 for a more complete list of attributes and criteria."
I have not failed. I've just found 10,000 ways that won't work" --Thomas Edison
UAT vs QA
what's the difference between UAT (User Acceptance Test) and QA Testing?
Re: UAT vs QA
What do your experiences and training tell you? How are these defined in your organization?