UI (browser) testing via Gitlab runner
SOLVED- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
UI (browser) testing via Gitlab runner
I'd like to use TestComplete, executed via Gitlab, to test a browser based system. To accomplish this, a remote session into the windows machine with TestComplete installed must already be active prior to the actual TestComplete test being executed, correct? Additionally the remote session must not be minimized nor can the machine which created the remote session be locked. Is there any way around these limitations.
Solved! Go to Solution.
- Labels:
-
Command Line
-
Integrations
-
Web Testing
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yep. I read that section. I based my questions on it.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The Tips and Workarounds section at the bottom of the page has your answers.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The minimize question is answered but the others remain. I'm looking for clarity/confirmation after reading the document. On the following:
1) Is an existing remote session required in the described context.
2) If an existing remote session is required is there any way the machine which created the remote session can be locked?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1) Yes, as per steps 3 & 4 here, the remote session must be created before you can contact it to start TestComplete.
https://support.smartbear.com/testcomplete/docs/testing-with/running/via-rdp/overview.html
2) Yes, if you disconnect from the remote session as described in the Tips and Workarounds. The disconnecting instructions are here
