mutx 0.1.18 → 0.1.19

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 26914453c8c0f4b526cef077dfe059faf56b729f
4
- data.tar.gz: 075d01dbb02baf52df6b02eddc1c70631bb609ac
3
+ metadata.gz: 375c6f62f3f415f25c138b7a6ff3423039df02f4
4
+ data.tar.gz: 5c01d117b6cd48ab5c3cc2d7546075a9d1441c9e
5
5
  SHA512:
6
- metadata.gz: 137a3d6e3aa87ce40cebddaa5a7302887e4ac105a7cdb6070ad5c893b7db28a5dc62672fe476652b5cdd3d094c20e7f0b8eb76bbc088656f0095050811a9fa54
7
- data.tar.gz: 7272f504537c168461ebdd3478ad706fe09056e0c657758d25f32ae102eb5a6cbca94c299112fb605cb25abe4da4d01fa3eac425c3a1d43b627aa4baceb3e6d0
6
+ metadata.gz: 797b738f26e447d029a8a3ebce085e4e3469bc2ced7bc8f60934deaaec22c76ac5a2ecfecebbd7d68985333a0bf427808f5940ee34bb9141ae058d3d22c25d8f
7
+ data.tar.gz: 9b046f399e6e3bec402e5563322bb8084c83da5be91424943edf4a9ec2a9c4faa65ecddf35e1fb9488d02eae479a14b4fb9059060222630cc4a2b42fbc8bdf83
data/README.md CHANGED
@@ -1,3 +1,4 @@
1
+ ![alt tag](https://raw.githubusercontent.com/romanrod/mutx/master/img/mutx_logo.png)
1
2
  Mutx (WIP)
2
3
  ==============
3
4
 
@@ -4,44 +4,48 @@ How do i use the api?
4
4
 
5
5
  Well, we want to do things as simple as possible, so we are using only GET requests. Everyone has a browser, so everyone has the possiblility to use Mutx.
6
6
 
7
- Returns the list of tasks
7
+ Returns the list of tasks or tests
8
8
 
9
- mutx/api/tasks
9
+ api/tasks
10
+ api/tests
10
11
 
11
- Returns the list of tasks that are running
12
+ Returns the list of running tasks or tests
12
13
 
13
- mutx/api/tasks/running
14
+ api/tasks/running
15
+ api/tests/running
14
16
 
15
17
  Returns the status of the given task id
16
18
 
17
- mutx/api/tasks/<task_id>/status
19
+ api/tasks/<task_id>/status
18
20
 
19
21
  Returns the task structure for the given task id
20
22
 
21
- mutx/api/tasks/<task_id>
23
+ api/tasks/<task_id>
22
24
 
23
25
  Returns all existing results
24
26
 
25
- mutx/api/results
27
+ api/results
26
28
 
27
29
  Returns the result for a given result id
28
30
 
29
- mutx/api/results/<result_id>
31
+ api/results/<result_id>
30
32
 
31
33
  Starts an execution
32
34
 
33
35
  Perform get to:
34
36
 
35
- mutx/api/tasks/<task_me>/run
37
+ api/tasks/<task_name>/run
36
38
 
37
- # pass custom parameters as query string like vmutx/api/tasks/:task/run?environment=RC&foo=bar
39
+ # pass custom parameters as query string like
40
+ api/tasks/:task/run?environment=RC&foo=bar
38
41
 
39
- # and if you want identify the execution, you can pass execution_name=your_execution_identification' as query string too.
42
+ # and if you want identify the execution, you can pass as query string too.
43
+ api/tasks/:task/run?environment=RC&foo=bar&execution_name=your_execution_identification'
40
44
 
41
45
  If execution starts succesfully, it will return a result id
42
46
 
43
47
 
44
48
  Returns the execution data for a given result id
45
49
 
46
- mutx/api/results/<result_id>/data
50
+ api/results/<result_id>/data
47
51
 
@@ -27,30 +27,48 @@ After adding the gem to your project, you can do:
27
27
 
28
28
  Mutx::Custom::Execution.add_data("my_data_key", "some value for data key")
29
29
 
30
+ Once the execution is finished, you can see the values through:
30
31
 
31
- Once the execution it is finished, you can see the values through:
32
-
33
- http::/host:port/mutx/api/results/<result_id>/data
32
+ api/results/<result_id>/data
34
33
 
35
34
  And you'll see something like:
36
35
 
37
36
  {
38
- type: "result",
39
- _id: 1427901370053,
40
- status: "stopped (Inactivity Timeout reached)",
41
- execution_data: {
42
- my_data_key: "some value for data key"
37
+ "type": "result",
38
+ "_id": 1427901370053,
39
+ "status": "finished",
40
+ "execution_data": {
41
+ "my_data_key": "some value for data key"
43
42
  }
44
43
  }
45
44
 
45
+ And you can navigate through the path of the JSON to get a value. Supose you have a result like this:
46
46
 
47
- Think about this for integration tests.
48
-
49
- ---------------------------------------
47
+ {
48
+ "type": "result",
49
+ "_id": 1427901370053,
50
+ "status": "finished",
51
+ "execution_data": {
52
+ "key": [
53
+ {
54
+ "sub_key1":"value_1"
55
+ },
56
+ {
57
+ "sub_key2":"value_2"
58
+ }
59
+ ]
60
+ }
61
+ }
50
62
 
51
- Path to output dir
52
- ============================
63
+ api/results/<result_id>/data?key.1.sub_key2
53
64
 
54
- If you want to save files you should use Mutx output dir path by using
65
+ And you'll see
55
66
 
56
- "#{Mutx::Custom::Execution.output_path}/<your_file_name.extension>"
67
+ {
68
+ "type": "result",
69
+ "_id": 1427901370053,
70
+ "status": "finished",
71
+ "execution_data": {
72
+ "sub_key2":"value_2"
73
+ }
74
+ }
@@ -1,117 +1,35 @@
1
1
  How to pass parameters to a test task execution?
2
2
  ==============
3
3
 
4
- As Mutx retrieve information from task's file called cucumber.yml allocated on projet root folder.
4
+ You can send parameters to a test or task execution and your tests can take that data to run in a certain way you need or want.
5
5
 
6
- You can send parameters to a test task execution and your tests can take that data to run in a certain way you need or want.
7
-
8
- To ask for parameters into a test task you have to set them up in cucumber.yml file.
9
-
10
- There are basically two types of fields you can show in test tasks (text field and select list).
6
+ There are basically three types of fields you use on task or test creation and or edition: text, select list or JSON
11
7
 
12
8
  This fields can be setted as required values and or with a default value.
13
9
 
14
- All custom parameters must be defined on each test task you need by using the custom parameter:
15
-
16
- #cucumber.yml
17
-
18
- regression: -t @regression runnable=true custom=[]
19
-
20
- Text field
21
- ---------------------
22
-
23
- To show a text field as a custom parameter you just have to define the name of the param
24
-
25
- regression: -t @regression runnable=true custom=[my_param]
26
-
27
- <form>
28
- <label class="col-sm-2 control-label" for="formGroupInputSmall">my_param</label><input type="text" name="my_param" value="" placeholder="" style="height: 34px; padding: 6px 12px; font-size: 14px; line-height: 1.42857143; color: #555; background-color: #fff; background-image: none; border: 1px solid #ccc; border-radius: 4px;">
29
- </form>
30
-
31
- ---------------------------------------
32
-
33
- If you want to define a default value just define the value like:
34
-
35
- regression: -t @regression runnable=true custom=[my_param:a_value]
36
-
37
- <form>
38
- <label class="col-sm-2 control-label" for="formGroupInputSmall">my_param</label><input type="text" name="my_param" value="a_value" placeholder="" style="height: 34px; padding: 6px 12px; font-size: 14px; line-height: 1.42857143; color: #555; background-color: #fff; background-image: none; border: 1px solid #ccc; border-radius: 4px;">
39
- </form>
40
-
41
- ---------------------------------------
42
-
43
- You can define the parameter as a required value by using \*
44
-
45
- regression: -t @regression runnable=true custom=[my_param:*]
46
-
47
- <form>
48
- <label class="col-sm-2 control-label" for="formGroupInputSmall">my_param</label><input type="text" name="my_param" value="" placeholder="" style="height: 34px; padding: 6px 12px; font-size: 14px; line-height: 1.42857143; color: #555; background-color: #fff; background-image: none; border: 1px solid #ccc; border-radius: 4px;">*
49
- </form>
50
-
51
- ---------------------------------------
52
-
53
- You can also define the parameter as required and with a default value by using:
54
-
55
- regression: -t @regression runnable=true custom=[my_param:a_value:*]
56
-
57
- <form>
58
- <label class="col-sm-2 control-label" for="formGroupInputSmall">my_param</label><input type="text" name="my_param" value="a_value" placeholder="" style="height: 34px; padding: 6px 12px; font-size: 14px; line-height: 1.42857143; color: #555; background-color: #fff; background-image: none; border: 1px solid #ccc; border-radius: 4px;">*
59
- </form>
60
-
61
- Select List
62
- ---------------------
63
-
64
- To provide a certain set of possible values that a test task can use, you can provide a custom parameter as a select list
65
- It is like a text field but just use () to provide the possible values separated by | (pipe char).
66
-
67
- regression: -t @regression runnable=true custom=[environment:(RC|IC|BETA|PROD)]
68
-
69
- <form>
70
- <label class="col-sm-2 control-label" for="formGroupInputSmall">environment</label><select id="environment" name="environment" style="height: 34px; padding: 6px 12px; font-size: 14px; line-height: 1.42857143; color: #555; background-color: #fff; background-image: none; border: 1px solid #ccc; border-radius: 4px;"> <option value="RC">RC</option> <option value="IC">IC</option> <option value="BETA">BETA</option> <option value="PROD">PROD</option> </select>
71
- </form>
72
-
73
- ---------------------------------------
74
-
75
- The first value on the list will be used as a default value if user does not select any other value from the list
76
- With this type of parameter you will ensure that the execution will expect a correct value to run. This is used to make a parameter required with a list of possible values
77
- ---------------------------------------
78
- But if you do not want to make a select list mandatory, you can use as a first value none to indicate the there is a null value. It is aimed to mimic that user does not select a value
79
-
80
- regression: -t @regression runnable=true custom=[environment:(none|RC|IC|BETA|PROD)]
81
-
82
- # none will be interpreted as an empty option, by using it at the first place on the list, you are setting this parameter as optional.
83
-
84
- <form>
85
- <label class="col-sm-2 control-label" for="formGroupInputSmall">environment</label><select id="environment" name="environment" style="height: 34px; padding: 6px 12px; font-size: 14px; line-height: 1.42857143; color: #555; background-color: #fff; background-image: none; border: 1px solid #ccc; border-radius: 4px;"> <option value=""></option> <option value="RC">RC</option> <option value="IC">IC</option> <option value="BETA">BETA</option> <option value="PROD">PROD</option></select>
86
- </form>
87
-
88
- ---------------------------------------
89
-
10
+ All custom parameters must be defined on Custom Parameters section:
90
11
 
12
+ When you associate a custom parameter to a task or test, the user of the task will be able to pass values to the execution
91
13
 
14
+ As an example, you can think about using custom parameters to provide the environmnet to the execution so your tests can point to a given environment
92
15
 
93
16
 
94
17
  How to get custom parameters
95
18
  ==============
96
19
 
97
- Once Mutx has got the custom parameters from cucumber.yml, you can get them whenever and wherever you want inside your code.
98
- You'll can do it by creating an instance of Mutx::Custom::Params
20
+ Well, custom parameters are passed to the execution in the same way you can pass to ENV constant.
21
+ From the execution, you can catch the custom parameter from ENV constant. In Ruby ENV is a Hash
99
22
 
100
- For example
101
- If you have defined a custom parameter like that: custom=[environment:(RC|PROD)]
23
+ For example, if you passed env=beta you will be able to catch the value like:
102
24
 
103
- So you will be able to get this parameter by the following way:
25
+ ENV['env']
104
26
 
105
- $CUSTOM = Mutx::Custom::Params.get
106
-
107
- $CUSTOM.environment
108
- # => will return the selected choice of environment param by the user.
109
27
 
110
- If you want to get all custom params in a hash you can use:
111
-
112
- $CUSTOM.all_params
113
- # will return a hash with all params and values {}
28
+ You can also use Mutx from you Ruby code in order to get the value from the custom parameter like:
29
+
30
+ require 'mutx'
31
+ $CUSTOM = Mutx::Custom::Params.get
114
32
 
115
- $CUSTOM.raw
116
- # Same as .all_params
33
+ $CUSTOM.env
34
+ # => will return the value passed to env custom param
117
35
 
@@ -9,4 +9,4 @@ Pressing this button:
9
9
 
10
10
  you will see a message with the url that starts the test task execution with the configured custom params and execution name
11
11
  This could be helpful when a story is in development process and your test is ready to be executed, so you can create a test task related to the history,
12
- set custom params, execution name and then share the link to de developer which is responsible about the history implementation
12
+ set custom params, execution name and then share the link to the developer which is responsible about the history implementation. Developer will be able to paste the url in the browser and start the execution instantly.
@@ -2,7 +2,7 @@ Results and details about them.
2
2
  ==============
3
3
 
4
4
  Each Test Suite execution creates a result. You can see them in Results section.
5
- You will see each Test Suite box with its results. If a Test Suite has more than three results, you'll see a green button that says `All results` for this test task to see all results for that test task
5
+ You will see each Task or Test box with its results. If a task or test has more than three results, you'll see a green button that says `All results` for this test task to see all results for that test task
6
6
  A result line looks like:
7
7
 
8
8
  <div class="panel panel-primary">
@@ -1,19 +1,24 @@
1
1
  What is Mutx?
2
2
  ==============
3
- *Basically it's about runnnig tests easily.*
3
+ *Basically it's about runnnig tests or tasks easily.*
4
4
 
5
- With Mutx, you don't have to install or configure nothing.
5
+ With Mutx, you don't have to install or configure nothing to run your tests or tasks than the mutx server.
6
6
  Just enter on your favourite web browser the url where Mutx is running for your test automation project,
7
- go to Suites and start the execution you need to run.
7
+ go to any test or task and start the execution you need to run.
8
8
 
9
9
  How to run tests?
10
10
  ==============
11
11
 
12
- You can run tests in Test Suites section. You'll find test tasks listed. Each test task involves many test (or not).
13
- If you want to know more about a test task you can mouse over the information icon which could have info about it
12
+ You can run tests in Tests section. You'll find test tasks listed. Each test task involves many test (or not).
13
+ If you want to know more about a test task you can click on the information icon which could have info about it
14
14
  Each test task saves its execution results in a database so you do not have to care about report because Mutx do that for you and store all reports as a history.
15
15
  You also can provide some parameters to the execution. This values are called Custom Parameters and you can set them up as your execution needs.
16
16
 
17
17
  Only test?
18
18
  ==============
19
- Well, why not use this to run any code?
19
+ Well, why not use this to run any code?
20
+
21
+ Cron tasks
22
+ ==============
23
+
24
+ Tasks can be cronned in order to run automatically after a given period of time again and again.
Binary file
@@ -0,0 +1,4 @@
1
+ <?xml version="1.0" standalone="yes"?>
2
+
3
+ <svg version="1.1" viewBox="0.0 0.0 247.30971128608923 247.30971128608923" fill="none" stroke="none" stroke-linecap="square" stroke-miterlimit="10" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"><clipPath id="p.0"><path d="m0 0l247.30971 0l0 247.30971l-247.30971 0l0 -247.30971z" clip-rule="nonzero"></path></clipPath><g clip-path="url(#p.0)"><path fill="#000000" fill-opacity="0.0" d="m0 0l247.30971 0l0 247.30971l-247.30971 0z" fill-rule="nonzero"></path><path fill="#000000" fill-opacity="0.0" d="m83.44774 76.74305l81.95276 0l0 75.77953l-81.95276 0z" fill-rule="nonzero"></path><path fill="#cc0000" d="m138.01024 119.0268l-12.09375 24.437508l-5.953125 0l-12.03125 -24.437508l0 28.156258l-9.984375 0l0 -44.734383l13.515625 0l11.515625 24.578125l11.578125 -24.578125l13.4375 0l0 44.734383l-9.984375 0l0 -28.156258z" fill-rule="nonzero"></path><path fill="#000000" fill-opacity="0.0" d="m93.96213 126.40189l-90.267715 0" fill-rule="nonzero"></path><path stroke="#000000" stroke-width="8.0" stroke-linejoin="round" stroke-linecap="butt" d="m93.96213 126.40189l-62.851025 0" fill-rule="evenodd"></path><path fill="#000000" stroke="#000000" stroke-width="8.0" stroke-linecap="butt" d="m31.111103 126.40189l8.99667 -8.996666l-24.718143 8.996666l24.718143 8.996666z" fill-rule="evenodd"></path><path fill="#000000" fill-opacity="0.0" d="m153.05222 126.40189l90.267715 0" fill-rule="nonzero"></path><path stroke="#000000" stroke-width="8.0" stroke-linejoin="round" stroke-linecap="butt" d="m153.0522 126.40189l62.85103 0" fill-rule="evenodd"></path><path fill="#000000" stroke="#000000" stroke-width="8.0" stroke-linecap="butt" d="m215.90323 126.40189l-8.996674 8.996666l24.718155 -8.996666l-24.718155 -8.996666z" fill-rule="evenodd"></path><path fill="#000000" fill-opacity="0.0" d="m123.50717 94.21465l0 -90.26772" fill-rule="nonzero"></path><path stroke="#000000" stroke-width="8.0" stroke-linejoin="round" stroke-linecap="butt" d="m123.507164 94.214645l0 -62.85102" fill-rule="evenodd"></path><path fill="#000000" stroke="#000000" stroke-width="8.0" stroke-linecap="butt" d="m123.507164 31.363626l8.996666 8.996668l-8.996666 -24.718143l-8.996666 24.718143z" fill-rule="evenodd"></path><path fill="#000000" fill-opacity="0.0" d="m123.50717 153.30473l0 90.267715" fill-rule="nonzero"></path><path stroke="#000000" stroke-width="8.0" stroke-linejoin="round" stroke-linecap="butt" d="m123.507164 153.30473l0 62.85103" fill-rule="evenodd"></path><path fill="#000000" stroke="#000000" stroke-width="8.0" stroke-linecap="butt" d="m123.507164 216.15575l-8.996666 -8.996658l8.996666 24.71814l8.996666 -24.71814z" fill-rule="evenodd"></path><path fill="#000000" fill-opacity="0.0" d="m214.61824 36.49638l-63.08661 63.086613" fill-rule="nonzero"></path><path stroke="#000000" stroke-width="8.0" stroke-linejoin="round" stroke-linecap="butt" d="m214.61826 36.49638l-43.70009 43.700085" fill-rule="evenodd"></path><path fill="#000000" stroke="#000000" stroke-width="8.0" stroke-linecap="butt" d="m170.91817 80.196465l0 -12.723206l-11.1167755 23.839966l23.839981 -11.116753z" fill-rule="evenodd"></path><path fill="#000000" fill-opacity="0.0" d="m213.29715 214.2986l-63.086624 -63.086624" fill-rule="nonzero"></path><path stroke="#000000" stroke-width="8.0" stroke-linejoin="round" stroke-linecap="butt" d="m213.29713 214.2986l-43.700073 -43.70009" fill-rule="evenodd"></path><path fill="#000000" stroke="#000000" stroke-width="8.0" stroke-linecap="butt" d="m169.59706 170.59851l12.723206 0l-23.839966 -11.1167755l11.11676 23.839981z" fill-rule="evenodd"></path><path fill="#000000" fill-opacity="0.0" d="m34.173836 36.49638l63.086617 63.086613" fill-rule="nonzero"></path><path stroke="#000000" stroke-width="8.0" stroke-linejoin="round" stroke-linecap="butt" d="m34.173836 36.49638l43.70008 43.700085" fill-rule="evenodd"></path><path fill="#000000" stroke="#000000" stroke-width="8.0" stroke-linecap="butt" d="m77.87392 80.196465l-12.723206 0l23.839966 11.11676l-11.11676 -23.839973z" fill-rule="evenodd"></path><path fill="#000000" fill-opacity="0.0" d="m34.173836 214.2986l63.086617 -63.086624" fill-rule="nonzero"></path><path stroke="#000000" stroke-width="8.0" stroke-linejoin="round" stroke-linecap="butt" d="m34.173836 214.2986l43.70008 -43.70009" fill-rule="evenodd"></path><path fill="#000000" stroke="#000000" stroke-width="8.0" stroke-linecap="butt" d="m77.87392 170.59851l7.6293945E-6 12.723206l11.116753 -23.839981l-23.839966 11.1167755z" fill-rule="evenodd"></path></g></svg>
4
+
@@ -167,8 +167,6 @@ module Mutx
167
167
  f.write "\n" unless content[-1] == "\n"
168
168
  f.write "mutx/\n" unless content.include? "mutx/"
169
169
  f.write "mutx/*\n" unless content.include? "mutx/*"
170
-
171
-
172
170
  f.close
173
171
  end
174
172
  end
@@ -24,7 +24,7 @@
24
24
 
25
25
  "inactivity_timeout" : 60,
26
26
 
27
- "kill_inactive_executions_after" : 300,
27
+ "kill_inactive_executions_after" : 600,
28
28
 
29
29
  "datetime_format" : "%d/%m/%Y %H:%M:%S",
30
30
 
@@ -1,6 +1,6 @@
1
- <html style='background-color: lightgrey'>
1
+ <html>
2
2
  <tbody>
3
- <img src="https://ci5.googleusercontent.com/proxy/A-quKChfId5qpYvXm_zcW-GEnolJEGQ4PeGkq50pBYmi5QHH-uoN22ysfGajMcE2lKvhMLJTemZwYYnh3MbzlR1IHzu6sZHu5VNS0pjR455lwdKxhgI8Og=s0-d-e1-ft#http://app2.dopplerfiles.net/Users/3778/Campaigns/8930766/logo.png" alt="Garbarino - Pensamos en vos" border="0" width="100%" style="display:block;margin:0 auto;border:0;max-width:300px;min-height:auto;outline:0" class="CToWUd"></a></td></tr>
3
+ <img src="https://raw.githubusercontent.com/romanrod/mutx/master/img/mutx_logo.png" alt="MuTX" border="0" width="100%" style="display:block;margin:0 auto;border:0;max-width:300px;min-height:auto;outline:0" class="CToWUd"></a></td></tr>
4
4
  <tr>
5
5
  <td align="left" style="font-size:10px;border-bottom:1px solid #e5e5e5">&nbsp;</td>
6
6
  </tr>
@@ -11,14 +11,14 @@
11
11
  <div class='container'>
12
12
  <br>
13
13
  <div class='well'>
14
- <h3 style='color:Black; font-size: 12px;'>Result for:<b style='color:Red; font-size: 14px;'>' <%= task_name %>'</b> execution </h3>
15
- <h6 style='color:Black; font-size: 12px;'><b>Result ID:</b><b style='color:Red; font-size: 14px;'> '<%= id %>'</b></h6>
16
- <h6 style='color:Black; font-size: 12px;'><b>Status:</b><b style='color:Red; font-size: 14px;'> '<%= status %>'</b></b></h6>
17
- <h6 style='color:Black; font-size: 12px;'><b>Duration:</b><b style='color:Red; font-size: 14px;'> '<%= time %>'</b> seconds</h6>
18
- <h6 style='color:Black; font-size: 12px;'><b>Summary:</b><b style='color:Red; font-size: 14px;'> '<%= info %>'
14
+ <h3 style='color:Black; font-size: 12px;'><b>Result for:</b>'<%= task_name %>' execution </h3>
15
+ <h6 style='color:Black; font-size: 12px;'><b>Result ID:</b>'<%= id %>'</h6>
16
+ <h6 style='color:Black; font-size: 12px;'><b>Status:</b>'<%= status %>'</h6>
17
+ <h6 style='color:Black; font-size: 12px;'><b>Duration:</b>'<%= time %>' seconds</h6>
18
+ <h6 style='color:Black; font-size: 12px;'><b>Summary:</b>'<%= info %>'
19
19
  <br>
20
20
  <br>
21
- <h3 style='color:Grey; font-size: 13px;'><b>Adjunto se encuentra el output de la ejecucion solicitada</b></h3>
21
+ <h3 style='color:Grey; font-size: 13px;'><b>The execution output is attached</b></h3>
22
22
  <h6>&nbsp;</h6>
23
23
  </div>
24
24
  <tr>
@@ -30,15 +30,9 @@
30
30
  <!-- Beggin Legacy Content -->
31
31
  <table width="100%" cellspacing="0" cellpadding="0" border="0" align="center" bgcolor="#FFFFFF">
32
32
  <tr><td width="100%" height="10" valign="top"></td></tr>
33
- <tr>
34
- <td width="100%" valign="top" bgcolor="#FFFFFF" style="font-family: sans-serif; font-size: 17px; line-height: 16px; color: #d22222; text-align: center;">
35
- GRACIAS POR UTILIZAR MUTX
36
- </td>
37
- </tr>
38
- <br>
39
33
  <tr>
40
34
  <td width="100%" valign="top" bgcolor="#FFFFFF" style="font-family: sans-serif; font-size: 15px; line-height: 16px; color: #d22222; text-align: center;">
41
- Este email es enviado desde una casilla autom&aacute;tica. Por favor, no lo responda.
35
+ This email is sent automatically. Please, do not reply
42
36
  </td>
43
37
  </tr>
44
38
  <tr><td width="100%" height="10" valign="top"></td></tr>
@@ -50,5 +44,4 @@
50
44
  </table>
51
45
  </td>
52
46
  </tr>
53
- <!-- End Legacy -->
54
47
  </html>
@@ -1,6 +1,6 @@
1
- <html style='background-color: lightgrey'>
1
+ <html>
2
2
  <tbody>
3
- <img src="https://ci5.googleusercontent.com/proxy/A-quKChfId5qpYvXm_zcW-GEnolJEGQ4PeGkq50pBYmi5QHH-uoN22ysfGajMcE2lKvhMLJTemZwYYnh3MbzlR1IHzu6sZHu5VNS0pjR455lwdKxhgI8Og=s0-d-e1-ft#http://app2.dopplerfiles.net/Users/3778/Campaigns/8930766/logo.png" alt="Garbarino - Pensamos en vos" border="0" width="100%" style="display:block;margin:0 auto;border:0;max-width:300px;min-height:auto;outline:0" class="CToWUd"></a></td></tr>
3
+ <img src="https://raw.githubusercontent.com/romanrod/mutx/master/img/mutx_logo.png" alt="MuTX" border="0" width="100%" style="display:block;margin:0 auto;border:0;max-width:300px;min-height:auto;outline:0" class="CToWUd"></a></td></tr>
4
4
  <tr>
5
5
  <td align="left" style="font-size:10px;border-bottom:1px solid #e5e5e5">&nbsp;</td>
6
6
  </tr>
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: mutx
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.18
4
+ version: 0.1.19
5
5
  platform: ruby
6
6
  authors:
7
7
  - Roman Rodriguez
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2016-08-17 00:00:00.000000000 Z
11
+ date: 2016-08-19 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: thor
@@ -309,14 +309,13 @@ files:
309
309
  - bin/mutx
310
310
  - documentation/api.md
311
311
  - documentation/api_execution_data.md
312
- - documentation/configuration.md
313
312
  - documentation/custom_parameters.md
314
313
  - documentation/document_mutx.md
315
314
  - documentation/link.md
316
315
  - documentation/results.md
317
316
  - documentation/start.md
318
- - documentation/suites.md
319
- - documentation/test_suite_information.md
317
+ - img/mutx_logo.png
318
+ - img/mutx_logo.svg
320
319
  - lib/.DS_Store
321
320
  - lib/generators/.DS_Store
322
321
  - lib/generators/task_rack.rb
@@ -1,13 +0,0 @@
1
- How to configure Mutx?
2
- ==============
3
-
4
- Mutx retrieve information from profiles file called cucumber.yml allocated on project root folder.
5
- You have to have this file into your project to work with Mutx.
6
-
7
- Mutx will show only those tasks marked as runnable as test tasks. To do this you only have to add a flag to each cucumber profile you want to expose as follows:
8
- Supose you have a profile called regression on cucumber.yml file
9
-
10
- #cucumber.yml
11
- regression: -t @regression runnable=true
12
-
13
- The flag `runnable=true` indicates to Mutx to expose the profile to be executed as a test task.
@@ -1,60 +0,0 @@
1
- How to use Test Suites in Mutx?
2
- ==============
3
-
4
- You can find test tasks on Test Suites section.
5
- Mutx will retrieve all profiles masked as runnable defined on cucumber.yml
6
- Each Test Suite can be executed by pressing Run button. The execution result could be identified after the execution by adding a label before pressing Run button
7
- For example, an identifier could be a release product version like r2.3.44. So you will be able to identify quickly the execution result later
8
- You can provide some parameters to the execution by using [Custom Parameters](/mutx/help/custom_parameters "Custom Parameters")
9
-
10
- A Test Suite looks like:
11
- ---------------------
12
-
13
- <div class="panel panel-primary">
14
- <div class="panel-heading" data-toggle="collapse" data-target="#multi">
15
- <h4 class="panel-title">multi</h4>
16
- </div>
17
- <div class="panel-body collapse in" id="multi">
18
- <ul class="list-group">
19
- <li class="list-group-item">Command: -t @multi</li>
20
- <li class="list-group-item">Last result:&nbsp;<a href="#" class="label label-danger" >Stopped (inactivity timeout reached)</a></li>
21
- <li class="list-group-item">Started on:&nbsp;24/05/47218 02:27:33</li>
22
- <li class="list-group-item">
23
- <form name="run" id="multi" method="get" action="#">
24
- <h4 title="This parameters will be passed to the test task execution">&nbsp;&nbsp;&nbsp;Custom Parameters</h4>
25
- <div class="container" style="width: inherit">
26
- <li class="list-group-item" style="position:relative; with=100%">
27
- <div class="form-group-sm">
28
- <label class="col-sm-2 control-label" for="formGroupInputSmall">environment</label>
29
- <select id="environment" name="environment" class="customParam" style="height: 34px; padding: 6px 12px; font-size: 14px; line-height: 1.42857143; color: #555; background-color: #fff; background-image: none; border: 1px solid #ccc; border-radius: 4px; font-weight:normal;">
30
- <option value="RC">RC</option>
31
- <option value="BETA">BETA</option>
32
- <option value="PROD">PROD</option>
33
- </select>
34
- <input type="text" id="otro0" name="otro" value="Enter otro" onfocus="if (this.value==&quot;Enter otro&quot;) this.value=&quot;&quot;;" placeholder="" style="display: none; height: 34px; padding: 6px 12px; font-size: 14px; line-height: 1.42857143; color: #555; background-color: #fff; background-image: none; border: 1px solid #ccc; border-radius: 4px;"></div>
35
- <div class="form-group-sm">
36
- <label class="col-sm-2 control-label" for="formGroupInputSmall">my param A</label>
37
- <textarea class="customParam" type="text" name="blabla" placeholder="" style="height: 34px; padding: 6px 12px; font-size: 14px; line-height: 1.42857143; color: #555; background-color: #fff; background-image: none; border: 1px solid #ccc; border-radius: 4px; max-width: 70%; max-height: 500px; min-height: 34px; min-width: 212px; font-weight:normal;"></textarea>
38
- </div>
39
- <div class="form-group-sm">
40
- <label class="col-sm-2 control-label" for="formGroupInputSmall">my param B</label>
41
- <textarea class="customParam" type="text" name="etc" placeholder="" style="height: 34px; padding: 6px 12px; font-size: 14px; line-height: 1.42857143; color: #555; background-color: #fff; background-image: none; border: 1px solid #ccc; border-radius: 4px; max-width: 70%; max-height: 500px; min-height: 34px; min-width: 212px; font-weight:normal;"></textarea>
42
- </div>
43
- <div class="form-group-sm">
44
- <label class="col-sm-2 control-label" for="formGroupInputSmall">my Param C</label>
45
- <textarea class="customParam" type="text" name="country" placeholder="" style="height: 34px; padding: 6px 12px; font-size: 14px; line-height: 1.42857143; color: #555; background-color: #fff; background-image: none; border: 1px solid #ccc; border-radius: 4px; max-width: 70%; max-height: 500px; min-height: 34px; min-width: 212px; font-weight:normal;"></textarea>
46
- </div>
47
- </li>
48
- </div>
49
- <br><br>
50
- <input type="submit" class="btn btn-success" value="Execute Suite">&nbsp;
51
- <input type="text" name="execution_name" class="customParam" title="This value could be used to identify the result execution from other execution of this task. E.g: You could use the release your are going to test" placeholder="Identify your execution" value="01APR15-1356" style="height: 34px; padding: 6px 12px; font-size: 14px; line-height: 1.42857143; color: #555; background-color: #fff; background-image: none; border: 1px solid #ccc; border-radius: 4px; font-weight:normal;">
52
- <button type="button" class="btn btn-default" aria-label="Left Align" data-toggle="modal" data-target="#myModal" onclick="javascript:starter_link(&quot;multi&quot;);">
53
- <span class="glyphicon glyphicon-star" aria-hidden="true">Link</span>
54
- </button>
55
- </form>
56
- </li>
57
- </ul>
58
- <a href="#" class="btn btn-default pull-center">All results(28)</a>
59
- </div>
60
- </div>
@@ -1,9 +0,0 @@
1
- How to provide information about a test task?
2
- ==============
3
-
4
- You can provide some information about a test task by adding info value to each task you need
5
-
6
- #cucumber.yml
7
- regression: -t @regression info=[This is to execute a regression tests task]
8
-
9
- This value `info=[Explaining text]` will show the icon <span class="glyphicon glyphicon-info-sign" aria-hidden="true"></span> where you can mouse over and read the text