From Fedora Project Wiki

(Created page with "{{QA/Test_Case |description= Slave machines |setup= # Ensure that Jenkins is running. |actions= # TODO |results= # user shouldn't encounter any error messages or stacktraces...")
 
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description= Slave machines
|description= Slave machines
{{result|fail}} Note this test will probably fail: [https://bugzilla.redhat.com/show_bug.cgi?id=1147978 rhbz#1147978] [https://bugzilla.redhat.com/show_bug.cgi?id=1147831 rhbz#1147831]


|setup=
|setup=
# Ensure that Jenkins is running.
# ensure that Jenkins is running
# you will need a virtual machine with SSH access for this test (or another physical machine)
#* you can get one easily with [http://rwmj.wordpress.com/2013/12/17/install-fedora-20-with-virt-builder/ virt-builder]
# this test case depends on [https://fedoraproject.org/wiki/Msrb:TestDay/Test_5 plugins] test case
|actions=
|actions=
# TODO
# go to http://localhost:8080/computer/new
# enter node name: "slave1" and select "Dumb Slave" option
# click OK
# set "Remote root directory" to "/tmp/jenkins"
#* this is just for test
# make sure that "Launch method" is set to "Launch slave agents on Unix machines via SSH"
# set "Host" to your VM's hostname/IP
# click "Add" next to "Credentials"
# from "Kind", select "Username with password"
# enter username and password which jenkins can use to access the VM
# click "Add"
#* you should be back in slave configuration screen and your credentials should be selected in "credentials" drop-down menu
# click "Save"
# go to http://localhost:8080/computer/slave1/
#* note "slave1" in URL is name of the slave, replace it with correct name if needed
# and click "Launch slave agent"
#* you should see console output which indicates that slave machine is up and running
# go to http://localhost:8080/computer/slave1/script
#* and try to execute command: println "uname -a".execute().text
# click "run"
#* you should see the output of "uname -a" executed on slave machine
|results=
|results=
# user shouldn't encounter any error messages or stacktraces, everything should work as described.
# user shouldn't encounter any error messages or unexpected stacktraces, everything should work as described
}}
}}

Latest revision as of 13:38, 30 September 2014

Description

Slave machines

Fail fail

Note this test will probably fail: rhbz#1147978 rhbz#1147831

Setup

  1. ensure that Jenkins is running
  2. you will need a virtual machine with SSH access for this test (or another physical machine)
  3. this test case depends on plugins test case

How to test

  1. go to http://localhost:8080/computer/new
  2. enter node name: "slave1" and select "Dumb Slave" option
  3. click OK
  4. set "Remote root directory" to "/tmp/jenkins"
    • this is just for test
  5. make sure that "Launch method" is set to "Launch slave agents on Unix machines via SSH"
  6. set "Host" to your VM's hostname/IP
  7. click "Add" next to "Credentials"
  8. from "Kind", select "Username with password"
  9. enter username and password which jenkins can use to access the VM
  10. click "Add"
    • you should be back in slave configuration screen and your credentials should be selected in "credentials" drop-down menu
  11. click "Save"
  12. go to http://localhost:8080/computer/slave1/
    • note "slave1" in URL is name of the slave, replace it with correct name if needed
  13. and click "Launch slave agent"
    • you should see console output which indicates that slave machine is up and running
  14. go to http://localhost:8080/computer/slave1/script
    • and try to execute command: println "uname -a".execute().text
  15. click "run"
    • you should see the output of "uname -a" executed on slave machine

Expected Results

  1. user shouldn't encounter any error messages or unexpected stacktraces, everything should work as described