User Acceptance
These notes were taken while studying using Mike Wheeler's Salesforce Courses.
User Acceptance Introduction (88)
User Acceptance Overview (89)
- User acceptance testing is end user testing performed in a sandbox or testing environment to verify that a project or enhancement works as intended, and that what was originally requested is what is being delivered
Agile Accelerator Installation (90)
- Getting Started with Agile Accelerator from Salesforce
Agile Accelerator Overview (91)
User Story and Acceptance Criteria - Test Script Example (92)
- In Agile Accelerator, different work items/user stories are associated to multiple individuals QA Engineer, Product Owner, UE Engineer, Assigned To, Performance Engineer, etc
- Also assigned to an Epic, or larger group of user stories, as well as a “Backlog Rank”
- Related lists include Acceptance Criteria, Change Lists, etc
- Each Work Item is also assigned a Status: New, Triaged, In Progress, Ready for Review, Fixed, QA in Progress, Closed
Working with Sprints in Agile Accelerator (93)
Configuring a Kanban Board in Agile Accelerator (94)
Completeness of Testing and Cross-Object Interoperability Considerations (95)
- There may be questions on the exam about testing across multiple objects
Identifying Good Candidates for Testers (96)
- Active Users/Power Users/Passive Users - all are good candidates for testers
Types of Testing (97)
- Types:
- Unit tests - key if you have done any kind of custom coding. These focus on the smallest bits of low-level code you’ve added to your org.
- Integration tests - test any code interacting with anything not native in your org
- Functional tests - verify that features work as defined in your technical requirements
- User Acceptance tests
- Performance tests
- The first 2-3 are typically performed by the technical team, but Functional and User Acceptance tests are completed by end users
Sandbox Consideration and Release Readiness - Sandbox Preview Guide (98)
- Sandbox Types and Templates
- “Full” sandboxes can support performance testing, load testing, and staging
- Sandbox Preview Web App
Code Coverage and Apex Test Cases (99)
- Organization’s code coverage makes a big difference with in go/no-go decision making
- Estimate code coverage by navigating to the Apex Classes page in Setup via: Setup > Quick FInd > “apex” > Apex Classes
- To deploy code to production you must have 75% code coverage
- Developers write test code to test any untested code ares