Endtest

Endtest

›Web Tests

Web Tests

  • How to create Web Tests
  • Finding elements in Web Applications
  • How to execute Web Tests
  • Assertions for Web Tests
  • IF Statements for Web Tests
  • Web Applications with restricted access
  • How to test in iframes
  • How to test in multiple tabs
  • How to test File Uploads
  • How to test File Downloads
  • How to test Emails
  • How to test PDF files
  • How to test Chrome Extensions
  • Dealing with reCAPTCHA
  • Dealing with Dynamic Locators
  • Dealing with Canvas Elements
  • Performing a Drag and Drop
  • Execute JavaScript
  • Testing WebRTC Applications
  • How to scroll in Web Tests
  • How to test Checkboxes
  • How to test Dropdowns
  • Dealing with Sessions
  • Web Crawler
  • Export Web Tests
  • Migrating from Selenium

Mobile Tests

  • How to create Mobile Tests
  • Finding elements in Mobile Applications
  • How to execute Mobile Tests
  • Assertions for Mobile Tests
  • IF Statements for Mobile Tests
  • How to scroll in Mobile Tests
  • Performing Complex Gestures

Advanced

  • Variables
  • Waits
  • Endtest API
  • Scheduler
  • Drive
  • Adding Collaborators
  • Computer Vision
  • Importing Test Cases
  • Using Loops
  • Data-driven Testing
  • Send API Requests
  • Read SMS
  • Execute SQL queries
  • Self-Healing Tests
  • Email Notifications
  • Slack Notifications
  • PagerDuty Notifications
  • Webhook Notifications
  • Automatic Backup
  • Advanced Settings
  • Multiple environments
  • How to stop a test
  • Utilities
  • Utilities API
  • Team
  • On-Premises

Integrations

  • Atlassian Jira
  • Slack
  • PagerDuty
  • Microsoft Teams
  • Discord
  • Mattermost
  • Jenkins
  • GitHub
  • Azure DevOps
  • GitLab
  • TeamCity
  • CircleCI
  • TravisCI
  • Bitbucket
  • Heroku
  • Bamboo Server
  • Test Case Management
  • SSO
  • BrowserStack
  • Sauce Labs

Dealing with Sessions

Introduction

In certain scenarios, you might want all the steps to be executed in the same session.

But in other scenarios, you might want to clear the session and the cookies before certain steps.

How do sessions work in Endtest

When you execute a Web Test, a real browser is started and the instructions from your test get executed in that browser.

All the test cases from that Web Test will be executed in the same browser session, one after another.

That means that if the test performs a Login in your web application at some point, it will stay logged in until the end of the entire test execution.

After the test execution is completed, the browser and the session get cleared and the data is deleted from the machine on which the test was executed.

How to clear the session

In some scenarios, you might need to clear the session and the cookies.

There are different methods in the Miscellaneous action that you can use:

  • Delete Cookies
  • Clear Local Storage
  • Clear Session Storage

Sessions for sending API requests

When using the Send API Request action, the API requests do not get sent from the browser.

Those API requests get sent from outside the browser.

That means the session information for those API requests is not stored in the browser.

More details about that are provided in the Sessions and Cookies section from that chapter.

Permanent storage in the Endtest Vault

You may encounter scenarios where a test execution needs to store information that can be retrieved by a different test execution.

For example, one test execution might store a unique value generated by your web application.

And another test execution might need to use that unique value.

This can be achieved by using the Endtest Vault.

← How to test DropdownsWeb Crawler →
  • Introduction
  • How do sessions work in Endtest
  • How to clear the session
  • Sessions for sending API requests
  • Permanent storage in the Endtest Vault
© Endtest Inc.