Artifacts in Salesforce Testing

In Salesforce testing, the development method commonly used is Agile/Scrum. The artifacts produced during Salesforce testing are similar to those of any other software testing project. Let's discuss some key artifacts typically involved in Salesforce testing: 

Test Plans 

Test plans outline the overall testing strategy, objectives, scope, and approach for the Salesforce project. They provide a high-level overview of the testing activities to be performed, including the types of tests, test environments, and resources required. Test plans ensure that testing efforts are well-organized and aligned with project goals. 

Test Cases 

Test cases are detailed documentation that specifies the steps to be executed, the expected results, and any test data required to validate the functionality of specific Salesforce features, objects, or processes. Test cases ensure thorough coverage of the system's functionality and facilitate efficient and systematic testing. They serve as a reference for testers to ensure all necessary scenarios are tested. 

Defect Reports 

Defect reports are crucial artifacts that document any identified defects or issues encountered during testing. They provide detailed information about the bug, including steps to reproduce, environment details, severity, and other relevant information. Defect reports help the development team understand and address the identified issues, enabling them to improve the system's quality. 

Reports and Dashboards 

Salesforce offers powerful reporting and dashboard functionalities that can be leveraged as artifacts in testing. Testers can create reports and dashboards within Salesforce itself to track testing progress, visualize test results, monitor key metrics, and generate insights into the overall testing effort. This allows for effective communication and monitoring of the testing activities. 

Other Test Artifacts 

Depending on the project's needs, additional artifacts such as test data, test scripts, test logs, traceability matrices, and test automation scripts may be created to support the testing process. These artifacts ensure documentation, traceability, and repeatability of the testing activities. Test data, for example, helps create realistic test scenarios, while test logs and traceability matrices help track testing activities and ensure coverage. 


It's worth noting that while the focus of Salesforce testing is often on identifying defects, other testing artifacts, such as test plans and test cases, are equally important. They help ensure comprehensive testing coverage, facilitate collaboration among team members, and provide a structured approach to testing. By utilizing Salesforce-specific artifacts like reports and dashboards, testers can also gain valuable insights into the system's performance and track testing progress effectively. 

Overall, producing and maintaining these artifacts throughout the testing lifecycle contributes to the success of Salesforce projects, promoting quality assurance, and ensuring that the Salesforce system meets the business requirements and delivers a seamless user experience. 

Building Blocks

   Quality Engineering within Salesforce

   Functional Testing

   Automated Testing

   People involved



Related wiki's

   Look and feel

   Architecture and Releases

   SuccessFactors explained