From Fedora Project Wiki

No edit summary
No edit summary
 
(4 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description= Script console
|description=Using script console.


|setup=
|setup=
# Ensure that Jenkins is running.
# Ensure that Jenkins is up and running
|actions=
|actions=
# run "curl -d 'script=Hudson.instance.version' http://localhost:8080/scriptText"
# run: <code>curl -d 'script=Hudson.instance.version' http://localhost:8080/scriptText"</code>
## the output should be Jenkins version, for example:
#* the output should be Jenkins version, for example:
<pre>
<pre>
Result: 1.575
Result: 1.581
</pre>
</pre>
# go to http://localhost:8080/script and experiment more:
# go to http://localhost:8080/script and experiment more:
## for example: "println(Jenkins.instance.pluginManager.plugins)", this should print list of all installed plugins
#* for example: <code>println(Jenkins.instance.pluginManager.plugins)</code>
#** this should print list of all installed plugins
#* more examples: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Script+Console
|results=
|results=
# there should be no failures or stacktraces printed on stdout/stderr
# there shouldn't be any error messages or stacktraces printed on a screen
}}
}}

Latest revision as of 11:55, 30 September 2014

Description

Using script console.

Setup

  1. Ensure that Jenkins is up and running

How to test

  1. run: curl -d 'script=Hudson.instance.version' http://localhost:8080/scriptText"
    • the output should be Jenkins version, for example:
Result: 1.581
  1. go to http://localhost:8080/script and experiment more:

Expected Results

  1. there shouldn't be any error messages or stacktraces printed on a screen