Testing Checklist for CRM Website
2017 Testing Checklist for CRM Website QA Specialist TestOrigen Software Testing Pvt. Ltd. 1/1/2017
WWW.TESTORIGEN.COM
PAGE 1
Testing Checklist for CRM Website
Functional Testing: Requirement Analysis Test Cases:
Tested by
Tested on Pass or Fail
Remarks
1. Testing of Association wide default 2. Testing of Access level 3. Testing of Accessibility to hidden information 4. Testing of Exchange forms 5. Testing of interconnection lost 6. Testing of Appropriate exemption handling 7. Stay away from information mismatch 8. Testing of Pre-Authorization 9. Testing of Post-Authorization
Data Integrity and Conversion Check:
Tested by
Tested on
Pass or Fail
Remarks
1. Test the duplication of data. 2. Test the hidden information is for sure hidden. 3. Test the Information maps accurately. 4. Test the new and refreshed information should be saved appropriately. 5. Test the no information is absent. 6. Test the Graphs should represent data accurately. 7. Test the data arranging module 8. Test the installation of CRM appropriately. 9. Test the Information saved in one field does not move to another field after saving it. 10. Check that information which shouldn't be editable is undoubtedly not editable. WWW.TESTORIGEN.COM
PAGE 2
Testing Checklist for CRM Website
Reporting and Integration Testing: Integration Test Cases:
Tested by Tested on
Pass or Fail
Remarks
1. The accuracy and dependability of information and reports from the new CRM arrangement should be tested to decide if they coordinate existing reports and how many, if any, reports must be revised. 2. Test the Exporting reports, do these reports trade in all formats with the right information. 3. Test that AND/OR filters work appropriately even with lots of filters affixed together. 4. Test that fields with no input value are not moving beyond filters incorrectly. 5. Test Label names should be the same regardless of where they show up. 6. Test the Unnecessary conditions i.e. producing a report at one store should not be subject to any activities at different stores. 7. Check the right information shows up when store-particular filters are connected. 8. Check the Reports should incorporate the right date and time of creation. 9. Test the Reports should demonstrate the right headings and construct forms. 10. Test the Report execution that is Data should populate the report a timely manner. 11. Filtering on date ranges should always be tested. WWW.TESTORIGEN.COM
PAGE 3
Testing Checklist for CRM Website
Regression and User Acceptance Testing: Regression and User Acceptance Test Cases:
Tested by Tested on
Pass or Fail
Remarks
1. Test the Documentation implies if the first documentation is inaccurate or the end-clients have undocumented necessities, at that point the documentation should be updated according to the actual customer’s need. 2. In CRM, customization to things like the network, structures, blueprint and layouts influences the ease of use. Unless test affirms the execution is acceptably simple to utilize, the application should not be released. 3. Test the functional Correctness and Completeness that is all components should be actualized accurately. 4. Test the Reliability that implies the CRM should meet or surpass benefit level uptime necessities and the end-clients should not need to sit tight quite a while for exchanges to transfer and information should be accessible constantly. 5. Test confidential means the Customer's details should be kept secret. 6. Test the application for a practical number of stores associated with a head office. 7. Check focuses should be observed for reaction time with an expanding number of open requests 8. Test the Sending order to demand 9. Test the Customer search. 10. Test the Payment processing on order settlement. WWW.TESTORIGEN.COM
PAGE 4
Testing Checklist for CRM Website
Security Testing: Penetration Test Cases:
Tested Tested Pass or by on Fail
Remarks
1. Attempt to specifically get to bookmarked page without login to the framework. 2. Check that past accessed pages should not available after log out i.e. Sign out and after that press the Back button to get page accessed before. 3. Check the valid and invalid passwords 4. Confirmed that essential i.e. sensitive data, for example, passwords, ID numbers, Mastercard numbers, and so forth should not get showed in the information box when writing. They should be encoded and in asterix format. 5. Check Is Right Click, View, Source debilitated? Source code should not be visible to client. 6. Check the timeout condition, after timeout client should not ready to explore through the site. 7. Check Are you prevented from doing direct searches by altering content in the URL? 8. ID/password authentication strategies entered the wrong password a few times and check if the account gets locked. 9. Confirm that Error Message does not contain pernicious data with the goal that programmer will utilize this data to hack site.
WWW.TESTORIGEN.COM
PAGE 5