UAT VS BAT

Differences between Build Acceptance Testing (BAT) and User Acceptance Testing (UAT):

Aspect	Build Acceptance Testing (BAT)	User Acceptance Testing (UAT)
Purpose	Ensure a newly created build is stable and ready for further testing.	Validate that the software meets business requirements and is ready for deployment.
Timing in SDLC	Conducted by the development team after creating a new build.	Occurs after system testing and before the final deployment of the software.
Executors	Usually performed by the development team.	Conducted by end users, business analysts, or QA teams representing end users.
Focus	Stability of the software build, checking acceptability for further testing.	Validation against business requirements, ensuring it meets user needs and is deployable.
Scope	Limited to basic functionality and stability testing.	Encompasses a broader set of tests, ensuring the software meets business goals, user expectations, and overall usability.
Outcome	Determination of whether the build is stable for further testing phases.	Validation that the software is ready for deployment based on business requirements and user satisfaction.
Scope of Testing	Primarily concentrates on basic functionality and stability.	Encompasses business process validation, user interface evaluation, and overall user satisfaction.
Test Environment	Typically conducted in a controlled development environment.	Ideally conducted in an environment closely mirroring the production environment.
Testing Techniques	Involves systematic and scripted testing. May include regression testing.	Can involve both scripted and exploratory testing, often in a more freeform manner.
Feedback and Communication	Feedback communicated within the development team for issue resolution.	Feedback communicated to both the development team and stakeholders, including insights on business alignment and user expectations.
Validation Criteria	Pass/fail criteria related to basic functionality and stability.	Pass/fail criteria aligned with business requirements and user satisfaction.
Responsibility	Typically the responsibility of the development team.	Involves end users, business analysts, or QA teams representing the end users. Collaborative effort between business and technical stakeholders.