How to Test Salesforce Console Apps

Updated 9 months ago by Copado Solutions

Salesforce Console type apps are constructed with a mix of Salesforce Classic, Salesforce1 technologies and a javascript framework called ExtJS, with a few issues when trying to automate navigation. In order to improve the quality of the tests, we recommend the following:

  • In the Copado Recorder extension, add "(^ext-gen[0-9]+)|(^ext-comp-[0-9]+)|(^tsk6_)|(^00B)|(^x-form-focus)|(^x-btn-over)|(^highlight)" (without the quotes) to Options -> Skip ids/names/classes matching.
    Also check Record non-essential clicks, to ensure that some special clicks are recorded.
    This will prevent the Recorder from creating locators that match a part of that regular expression. Console apps have dynamically generated Ids that can change between the recording and the execution of the tests.
  • Always close any existing tabs and manually add the command copadoContext startConsoleApp right after the open /console command.
    This will ensure that the 'tabs' (which are actually iframe html tags) are closed, and the test execution will run in the same order as it was recorded, regardless of the previous state.
  • Do not rely on list views to select an existing record. Use instead the search feature.
    Since the list order or last viewed records can change between the recording and the executions (or between executions), this may lead to erratic failures.
  • Interaction Log at the bottom of the page is time sensitive, after clicking on Save Log and the other actions, a pause between 3-5 seconds is recommended.


How did we do?