Sometimes, an automation scenario may require performing steps in two separate browser sessions that don't share cookies and cache. In this article, we'll describe how to manage multiple browsers within the same test script and switch between them.
Sometimes you want to test a process which requires a handoff between departments and would involve different testers to complete the full range of functionality. This article describes how to set that up, using a test set.
Sometimes you will have a situation where you want to run the same test cases on multiple different platforms (e.g. Windows/Linux, IE/Firefox/Chrome, MySQL/Oracle/DB2), and be able to distinguish the results. This article describes several different ways to do this.
Sometimes you have a web test where you need to test the contents of two browser tabs at the same time in Google Chrome. For example you may have an application which opens up a second browser tab and you want to test that changes in the second tab show up correctly in the first tab. This article describes how to perform this kind of testing.
When you have a multi-select list in a web application, you may need to check which items are selected, or to check whether or not a particular item is selected. This article illustrates how to do that.
When running a test you will often want to make sure there are no other browser windows open. This is commonly done either at the start or end of the test. This article describes how you do this.
This article is obsolete. With Selenium-based connectors (default option since Rapise 7.3) opened browser windows are longer an issue. One may continue to use regular browsers. Rapise will use isolated browser profiles to run tests.