warriorframework/release_notes.txt at master · lukemanhakkim/warriorframework · GitHub

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
Release: Ninja

Version: warrior-3.12.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 3.12.0

=====================
  2. Version Details
====================

You are on Release Ninja, Version warrior-3.12.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-2002] – Support for new core keyword verify_response_in_console_log  in REST Actions. The  keyword can used validate Asynchronous events in Warrior Console logs.
[WAR-2103] – Testdata Block Enhancement’s.
               To skip subsequent command execution in testdata block if one of the command fails in testdata block. Option added return_on_fail
               Provision to give sleep before end prompt match to collect full response from command output. Option added sleep_before_match
               To store command status and command in data repository
[WAR-2122] –  Option to disable sensitive data logging. Option added log in testdata block.
[WAR-1825] -  Support regex in verify_data keyword to verify large responses.
[WAR-1668] –  New keyword fetch_in_repo in common driver which prints required data repository value
[WAR-2099] -  Support to take in multiple xpath for validation in netconf.
[WAR-1437] –  To display git  branch information in the Warrior Console logs.

------------ Bugfixes: ---------------------------------

[WAR-1722] - Warhorn isn't checking pip install status correctly and ignore stderr output.
[WAR-1771] - On Error should be ignored until the last substep when a step is in runmode.
[WAR-1878] - pNote prints gets logged twice in result files.
[WAR-2001] - The restAPI keyword "Verify Response" should support environment support in json file which is provided as input argumentt in verification json file in verify_response
[WAR-2095] - Warrior wrapper doesn't allow to create setup/teardown steps without onError
[WAR-2097] - SNMP: start trap listener key word is not working properly when running the Suite file
[WAR-2098] - Fix relative filepath from wrapper file.
[WAR-2104] - selenium test cases are failing in travis
[WAR-2118] -  'Test step number' of failed test step which invokes another test step by using 'execute_and_resume.
[WAR-2140] - mock fix for verify_cmd_response


=================================================
  3. Procedure to get a specific version of Warrior
=================================================
1. Clone warriorframework
     $ git clone https://github.com/warriorframework/warriorframework.git
2. Go to warriorframework directory
     $cd warriorframework
3. To check the list of versions available, execute "git tag --list" command
     $ git tag --list
       warrior-3.1.0
       warrior-3.1.1
       warrior-3.2.0
       warrior-3.3.0
       warrior-3.3.1
       warrior-3.4.0
       warrior-3.5.0
       warrior-3.6.0
       warrior-3.7.0
       warrior-3.8.0
       warrior-3.9.0
       warrior-3.9.1
       warrior-3.10.0
       warrior-3.11.0
       warrior-3.12.0
4. 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 not using a standard release version of warrior framework
           and hence it may not be a stable tested version.


5. To switch to a specific version from master, execute 'git checkout <version_name>' command.
    $ git checkout warrior-3.12.0
     Note: checking out 'warrior-3.12.0'.
     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 abcba40... update version and release notes for 3.12.0
6. Execute git branch command to verify the active version.
   $ git branch
    * (detached from warrior-3.12.0) master
    - * indicates the active version.
7. Switch from one version to another (current=warrior-3.12.0, switch to warrior-3.11.0)
    $git checkout warrior-3.11.0
    Previous HEAD position was 6cea565... Update version.txt
    HEAD is now at ba0fdc8... Update version.txt
    $git branch
    * (detached from warrior-3.12.0)     master
8. Switch to master branch again.
   $ git checkout master
    Previous HEAD position was ba0fdc8... Update version.txt
    Switched to branch 'master'
   $ git branch    * master