Forum Discussion

New Contributor

3 years ago

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 pr...

Command Line

Integrations

web testing

Marsha_R
3 years ago
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

https://support.smartbear.com/testcomplete/docs/testing-with/running/via-rdp/keeping-computer-unlocked.html

Marsha_R

Moderator

Take a look here

https://support.smartbear.com/testcomplete/docs/testing-with/running/via-rdp/overview.html

bmiller1

New Contributor

3 years ago

Yep. I read that section. I based my questions on it.

Marsha_R
Moderator
3 years ago
The Tips and Workarounds section at the bottom of the page has your answers.
- bmiller1
  New Contributor
  3 years ago
  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?
  - Marsha_R
    Moderator
    3 years ago
    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
    
    https://support.smartbear.com/testcomplete/docs/testing-with/running/via-rdp/keeping-computer-unlocked.html

Recent Discussions

Onscreen Object Selector Slowness
2 days ago
SSpade
aqObject.CheckProperty() slowness
2 days ago
SSpade
Problem with generated data table and keyword test
5 days ago
KevserSaruhan
WebView2 support does not work
6 days ago
DanNad
System checks for Object for every test
6 days ago
hkonakanchi

Forum Discussion

UI (browser) testing via Gitlab runner

Related Content

Soapui Maven with Gitlab - The gitlab job succeeds despite the failure of tests

Zephyr Scale Integration with Gitlab

Gitlab CI/CD license issue

Gitlab with Open API

Headless browser

Recent Discussions

Onscreen Object Selector Slowness

aqObject.CheckProperty() slowness

Problem with generated data table and keyword test

WebView2 support does not work

System checks for Object for every test