Skip to content

QA_Salesforce.md

Latest commit

 

History

History
45 lines (36 loc) · 2.09 KB

QA_Salesforce.md

File metadata and controls

45 lines (36 loc) · 2.09 KB

Salesforce QA - Code Challenge

The main objective of this assignment is to measure the candidate’s test engineering skills.

General Information

Please read the information below carefully before proceeding to the next section.

  • Code challenge should be submitted as a link to a public git repository (github.com is preferred).
  • We are looking for code that we can Trust! Follow best practices for coding & automation (OOP, POM, reusable, clean, documented code, etc).
  • Implementations focusing on quality over feature completeness will be highly appreciated. Do not feel compelled to implement everything and even if you are not able to complete the challenge in the given time, please submit the work done anyways.
  • Remember, A test passing an execution does not mean that the application works as expected. Ensure you look out for false negative and false positive tests.
  • If you have any questions about this challenge, please do not hesitate to reach out to us. Good Luck!

Environment Details

First Scenario

  1. Navigate to the salesforce URL above.
  2. Login to the portal using the credentials above.
  3. Navigate to 'Service' App.
  4. Create a new 'Account'.
  5. Create a new 'Contact' using the same Account as above.
  6. Create a new 'Case' and enter values for all fields (Select the Account and Contact created above).

Conditions

  • Include test cases for positive and negative scenarios.
  • Perform necessary assertions for each page and action performed.
  • Generate a report for executed test cases.

Second Scenario

  1. Navigate to the salesforce URL above.
  2. Login to the portal using the credentials above.
  3. Navigate to 'Service' App.
  4. Navigate to 'Cases'.
  5. Search for the case created in the first scenario above.
  6. Change 'Case Owner' to Queue Name:'Dummy Queue'.

Conditions

  • Perform necessary assertions for each page and action performed.
  • Generate a report for executed test cases.