Salesforce QA Engineer Interview Questions

Salesforce aims to reduce the feedback loop time for its CI/CD pipeline by running tests in parallel across multiple agents. Your task is to design a function to manage the parallel execution of test cases.
- def run_tests_in_parallel(tests: List[str]) -> List[Result]: takes a list of test names and runs them concurrently, returning their results.Example 1:
Input: tests = ['test_login', 'test_checkout', 'test_dashboard']
Output: [Result(success=True), Result(success=False), Result(success=True)]
Explanation: Runs the listed tests in parallel and returns their execution results.Constraints:
- tests will contain between 1 and 100 test names, each string not exceeding 30 characters.

Salesforce relies on maintaining a highly reusable and scalable test automation framework for its web applications. Utilizing the Page Object Model (POM) can enhance maintainability and readability of tests.
You are tasked with creating a framework where each page of the application is represented by a separate class. Each class contains methods that interact with the elements of that specific page.
- class LoginPage: represents the login page.
- def enter_username(username: str) -> None:: inputs the username into the provided field.
- def enter_password(password: str) -> None:: inputs the password into the provided field.
- def click_login() -> None:: submits the login form.Example 1:
Input: username = 'admin', password = 'password123'
Output: None
Explanation: The methods should invoke actions to fill the username and password fields, then click the login button.Constraints:
- username and password should be strings limited to 20 characters each.
- The methods should not return any value after their execution.

Salesforce needs to ensure that its applications perform well under heavy load. Design a system that orchestrates the execution of load tests across different endpoints to measure performance metrics.
- class LoadTestOrchestrator:
- def start_load_test(endpoint: str, load: int) -> None:: initiates a load test on the given endpoint with the specified load.
- def get_results(endpoint: str) -> List[Metric]: returns the performance metrics after the test completes.Example 1:
Input: start_load_test('/api/v1/users', 100) followed by get_results('/api/v1/users')
Output: [Metric(response_time=150, success_rate=95)]
Explanation: Initiates a load test with 100 concurrent users and fetches the performance metrics afterward.Constraints:
- endpoint can be any valid string up to 100 characters.
- load is between 1 and 10,000 users.

Salesforce is facing challenges with flaky tests that produce inconsistent results, causing delays in the release process. You need to design a system that analyzes test results over time to identify patterns of flakiness.
- class FlakyTestDetector:
- def add_result(test_name: str, result: bool) -> None:: records the result of a single test execution.
- def is_flaky(test_name: str) -> bool:: returns whether a test is considered flaky based on its results.Example 1:
Input: add_result('test_login', True) followed by add_result('test_login', False) followed by is_flaky('test_login')
Output: True
Explanation: The test has produced different results in consecutive runs, indicating flakiness.Constraints:
- test_name can be any string up to 50 characters.
- This tool should handle results for a minimum of 1 and a maximum of 1000 different tests.