Validating New Versions
- Graceful degradation — Apex unit tests can make configuration changes during a test run to confirm features work as expected when enabled or disabled. (TBD)
- Health Check — The packaging and business orgs continue to pass the Salesforce Security Health Check following each major release, with a score of 80% or above. New subscriber orgs are reviewed with the Salesforce Optimizer before launch. (TBD)
- Release Ready — The packaging and pre-launch production orgs kept in a state of continual release readiness. (TBD)
- Scope / Docs — Validation includes the relevant help topics and other documentation (ApexDocs, Developer Guides). (TBD)
- Scope / Tests — Validation includes both regression tests and feature acceptance tests, in automated and exploratory form. #TestLikeACustomerr (TBD)
- Toggle Tests — Validations are performed with all features toggled off, all features toggled on, and with only new features toggled on. (TBD)
- Validation — The latest work increment, is examined at the close of each sprint, to determine whether the version is ready-for-primetime. For MPs, a milestone version is validated. For CSs, a full staging sandbox is validated. For MPs, patch versions are run through the same gauntlet as major versions. (TBD)
- Version Certification — Each new version is validated following a detailed checklist and exploratory test plan. If all checklist items pass, the version is certified for production use. Uncertified versions are deprecated. (TBD)
- Version Issue Resolved — The issue for the version is resolved in the New Version issue tracker and indicates its resolution status (failed certification, certified but not deployed, certified and deployed). (TBD)