xUnit Results Path: (optional) specify where you would like to store the results reports in xUnit format for publishing in a later step.Additional Parameters (optional): additionally provide any other API parameters or custom variables in JSON format (eg, ).This feature allows you to section off specific sequences into reusable sub-tests and include them within other tests. Keep your tests modular and DRY (Don’t Repeat Yourself) by using our test import feature.
Start URL (optional): provide the alternative URL of your test environment to execute your test against. Below are five best practices that we suggest when building Ghost Inspector tests, and automated browser tests in general.API Key: provide your Ghost Inspector API key ( provided in your account).Suite ID: specify the ID of the Ghost Inspector test suite you wish to execute.Once the task has been added, you have the ability to customize your build step: Trigger tests from your Azure DevOps buildĪdding Ghost Inspector test suite execution to your Azure DevOps build is as simple as adding a new Ghost Inspector task. Notify your team when things haven't gone as expected.Customize and override test settings in advance or at runtime.Catch and review Visual Regressions with our screenshot comparison tool.Monitor the functionality of your website or application on a schedule or on demand.Build and manage your tests with our Visual Editor.Painlessly record tests in your browser using our browser extension.Ghost Inspector is a powerful tool in your QA arsenal to ensure that your websites and application are behaving as expected. It carries out operations in a browser, the same way a user would, to ensure that everything is working properly.Ĭheck out our Getting Started page for more information. While logged in to your Jira account, from the homepage, click Jira Settings, then Apps, then Find New Apps. Ghost Inspector is an automated website testing and monitoring service that checks for problems with your website or application. The CrossBrowserTesting integration add-on only needs to be installed ONCE from your Jira admin console, then each CrossBrowserTesting account that needs to be authorized can be added via the Jira UI.
0 kommentar(er)
