forked from warriorframework/warriorframework
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathrelease_notes.txt
executable file
·136 lines (118 loc) · 5.26 KB
/
release_notes.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
Release: Ninja
Version: warrior-3.1.0
===================
1: Release details
===================
This is release Ninja of Warrior Test Automation Framework
-------------------------------
1.1: List of available releases
-------------------------------
1. Ninja = warrior-3.1.0 to current
==================
2. Version Details
==================
You are on Release Ninja, Version warrior-3.1.0 of Warrior Framework.
Procedure to get a specific version is available in section-3 of this document.
+++++++++++++++++++++++++++++++++
2.1. Change log for this release
+++++++++++++++++++++++++++++++++
-------------
New Features:
-------------
[WAR-547] - Improve the structure of the built-in tests
[WAR-855] - Update print error, info, debug and all other print utils to write to result file same way like pNote
[WAR-885] - SNMP Warrior MIB Browser
[WAR-934] - Selenium KWs: Selenium functional tests need to be updated as the elements on the webpages that they were accessing have changed
[WAR-939] - WARHORN: allow --user option when installing dependency
[WAR-940] - If a testcase is in the "Draft" state, Warrior should not run the testcase as it would contain keywords and/or drivers that have not been developed yet.
[WAR-958] - OSS: Create/move tests folder inside Warrior/Katana/Warhorn directories
[WAR-1099] - Create JUnit file during execution
[WAR-1106] - OSS: Change warhorn default config file so new users can run without any changes
[WAR-1115] - Move cli_tests data file into a separate folder
[WAR-1136] - As a user, I want to set many ENV variables and pass it to a file
[WAR-1132] - Option to substitute WF data repository values in Testdata blocks
[WAR-1182] - Update .travis.yml file with the new project name
-------------
Improvements:
-------------
[WAR-1131] - VAR_SUB substitution doesn't happen when used with "verify="${[VAR_SUB].verify_commit}""
---------
Bugfixes:
---------
[WAR-721] - Junit is not generated correctly for iterative parallel testsuite
[WAR-760] - Keyword waitfor_subscription fails after timeout
[WAR-837] - MIBS Loading from GIT url not working.
[WAR-865] - Selenium keyword mentioned in the description returns pass when it should have failed
[WAR-879] - SNMP: keyword start_tarp_listener should be changed to start_trap_listener
[WAR-935] - runmode value taken as one less
[WAR-936] - Issue : Prints "-I- failed: failure action= Abort" in all Passed steps.
[WAR-978] - WNetwork expects "%" in response to ping. "%" may also be prompt in most systems
[WAR-982] - Change in file utils in resolving the absolute path has impacted the demo action files.
[WAR-983] - From 2.9 Selenium element config files in data files have become unresolvable.
[WAR-1033] - selenium : Need to correct selenium_generic_tc_10.xml
[WAR-1064] - Warrior hang in certain scenario when verify_on is set
[WAR-1098] - Junit file format is incorrect
[WAR-1121] - TS with parallel_kw tc throws error when trying to combine junit result
[WAR-1155] - Selenium: Need to correct the relative paths of the config files which is mentioned in data files
[WAR-1169] - Due to rearrangement of version file in the new repo, details of the version will not be logged in the log file.
[WAR-1066] - copy option in test data doesn't list the step number to be copied
[WAR-1180] - Change the import for print utils and other files to prevent loop import
=================================================
3. Procedure to get a specific version of Warrior
=================================================
1. Clone warrior main
$ git clone https://github.com/warriorframework/warriorframework.git
2. go to warrior_main directory
$cd warrior_main
3. To check the list of versions available, execute "git tag --list" command
$ git tag --list
3.0
3.1
3.2
3.3
3.4
$
3. To Check the current version you are at, execute "git branch" command
$ git branch
* master
$
- * indicates the active version.
- In the above example master is the active version.
- If the active version is master it means you are using a version of warrior framework that is under development. It is
not a stable tested version.
4. To switch to a specific version from master, execute 'git checkout <version_name>' command.
$ git checkout 3.4
Note: checking out '3.4'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b <new-branch-name>
HEAD is now at 146313d... reduce command timeout, wait after timeout=60
$
5. Execute git branch command to verify the active version.
$ git branch
* (HEAD detached at 3.4)
master
$
- * indicates the active version.
6. Switch from one version to another (current=3.4, switch to 3.3)
$ git checkout 3.3
Previous HEAD position was 146313d... reduce command timeout, wait after timeout=60
HEAD is now at ecb6373... WAR-180, handle nd prompt on timeout
$
$ git branch
* (HEAD detached at 3.3)
master
$
7. Switch to master branch again.
$ git checkout master
Previous HEAD position was ecb6373... WAR-180, handle nd prompt on timeout
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
$
$
$ git branch
* master
$