... | ... | @@ -73,7 +73,7 @@ |
|
|
* Control the Amazon EC2 instances. See "Remote Access".
|
|
|
|
|
|
* Start the Selenium servers
|
|
|
* Linux: From a separate screen window, execute "~/seleniumServer.sh" (must this be done from the GUI?)
|
|
|
* Linux: From a separate screen window, execute "~/seleniumServer.sh". At least when a VPC is used, it seems necessary to connect to the GUI (maybe export DISPLAY or something to run from the command line?).
|
|
|
* Windows: Open "Windows PowerShell" and execute ".\seleniumServer.bat"
|
|
|
* If you have any problem to interrupt Selenium instances you may stop the server and run it again.
|
|
|
|
... | ... | @@ -127,7 +127,7 @@ IPs so that we won't be charged anymore. See "Stopping the Testing Framework". |
|
|
* Use a SSH client to connect to the instance.
|
|
|
* Use the "screen" command to handle several windows. Quick guide to the screen environment: use "Ctrl + a, Ctrl + c" to create a new window, "Ctrl + a, Ctrl + n" to move to the next window, "Ctrl + a, Ctrl + p" to move to the previous window, use the "exit" command to close the current window and finally "Ctrl + a, Ctrl + d" to detach the screen session. When you detach a screen session, all the servers will keep running even if you logout from the SSH session. You can restore your screen session when you connect again with the command "screen -r" (provided the machine has not been stopped since your last connection).
|
|
|
* In one screen window, use "~/init.sh" to start the VNC server. On the machine 10.0.0.30, this will also mount the mathjaxtest bucket on ~/MathJax-results/ and start the task handler.
|
|
|
* If necessary, you may use a VNC client to connect to the instance.
|
|
|
* Use a VNC client to connect to the GUI.
|
|
|
|
|
|
* Windows Instance
|
|
|
* Use a RDP client to connect to the instance.
|
... | ... | |