📄️ Create Browser Test
A Browser Test allows running your end-to-end test scenario using real browsers from our cloud environment. We leverage Playwright framework to executing the test scenario. The scenarios can be automated using our no-code editor or by adding scripts written in Javascript.
📄️ Create test from recipe
Navigate to Home page to see a list of Browser Test recipes that can be readily used for most common test scenarios.
📄️ Recording Tests
DevRaven Recorder
📄️ Local environment setup
When you are developing a new Browser Test scenario, instead of writing Javascript code directly in the browser window, you can create the script using your favorite IDE and execute the script from your local environment before setting it up for monitoring in DevRaven.
📄️ Edit Browser Test
A previously configured Browser Test can be edited from Edit Test page.
📄️ Running a Test
Browser Tests can be executed manually or can be scheduled to run automatically at predefined intervals.
📄️ Browser Test Results
Browser Test Results page shows the historical monitoring results for the test.
📄️ Supported Browsers
Playwright provides Chromium (Google Chrome, Microsoft Edge), Firefox, Webkit (Apple Safari) browsers for running the test. We only support running the test in headless mode. Refer Playwright Browsers documentation for more details. We only support running tests against the packaged recent builds, running tests using on stable and beta channel builds is not supported.
📄️ Capturing Screenshots
We support capturing screenshots while running the tests. We support a capture of up to 10 screenshots per test. Any screenshots captured during the test execution are automatically saved and shown in the test results page.
📄️ Scrape content on a page
Playwright scripts can be used to navigate through web pages and capture content on a page. Playwright's Locator API allows find specific elements on a page and interact with those page elements.
📄️ API Tests
We also support executing REST API tests using Playwright scripts.
📄️ Test assertions
We support performing assertions using Jest's expect framework or chai.js framework.
📄️ Third party libraries
Our Browser Test environment comes packaged with the following third party libraries that can be readily used in your tests.
📄️ Test Execution Time
The maximum allocated runtime for each Browser Test is 2 minutes. Your test must complete within 2 minutes for capturing the test result.
📄️ Using Environment Variables
Browser Tests can leverage variables defined in Environments instead of hardcoding values in your test. Any variables defined in the associated environment can be accessed in the test script.
📄️ Preserving state values
We recommend that the monitors not have dependencies on any state values. However, there can be scenarios where a test may have dependency on a value previously created in another monitor.
📄️ Available APIs
Following DevRaven APIs are available for use in your scripts during execution of Browser Tests.
📄️ HTTP Requests with axios
You can use axios and other third-party libraries from your monitoring scripts.
📄️ No-code Editor
The No-code Editor allows you to create an end-to-end Browser Test by composing pre-defined actions to execute in a sequence. The editor has support for several most common actions to automate a scenario. You add add steps for each interaction or assertion you would to perform during the execution of the test. Drag and drop is also supported to change the execution sequence of each action.
📄️ Tracing
DevRaven supports capturing network requests and console log messages while executing browser based checks. This is especially useful to get visibility into any failing network requests or any unknown errors while executing your tests.