- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2024 02:37 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2024 03:53 AM
QA instance in ServiceNow is used to test the functionality by testing team.
UAT instance in ServiceNow is used to test the actual functionality by the business team from customer to see if everything is configured as per the business need
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2024 03:56 AM
Practically speaking, its a win if you can convince organizations there's a difference *at all*.
A QA Tester tends to be a dedicated role that's closer to the devs than the stakeholders. "Hey we built XYZ, make sure it works like we think we built it"
A UAT Tester is rarely a dedicated role. UAT = user acceptance, and thus the users of the actual thing need to be involved. "Hey, we told you to build XYZ, and now we're going to see if you did"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2024 03:53 AM
QA instance in ServiceNow is used to test the functionality by testing team.
UAT instance in ServiceNow is used to test the actual functionality by the business team from customer to see if everything is configured as per the business need
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2024 03:56 AM
Practically speaking, its a win if you can convince organizations there's a difference *at all*.
A QA Tester tends to be a dedicated role that's closer to the devs than the stakeholders. "Hey we built XYZ, make sure it works like we think we built it"
A UAT Tester is rarely a dedicated role. UAT = user acceptance, and thus the users of the actual thing need to be involved. "Hey, we told you to build XYZ, and now we're going to see if you did"