Robotframework request package upgrade changes

Current working package version
robotframework-requests 0.7.2

To Test:
pip3 install robotframework-requests -U
or

Robotframework request package upgrade changes

Current working package version
robotframework-requests 0.7.2

To Test:
pip3 install robotframework-requests -U
or
# Once this commit is merged.
pip3 install -r requirements.txt

Version latest:
robotframework-requests 0.9.3

Refer Documentation:
https://marketsquare.github.io/robotframework-requests/doc/RequestsLibrary.html

What is not changed:
- The test cases under directory tests/ is not modified and is
deprecated but you can continue using it with older package
and configuration using

git clone -b v3.0-stable https://github.com/openbmc/openbmc-test-automation

Tested:
Upstream HW_CI test list, firmware code update and few other
test suite like ipmi, certificate, dumps, ffdc and redfish
test suites.

Note: I have not tested end to end, so it is likely there could be
grey areas where it could fail but should be minor w.r.t
response data format.

Resolves: openbmc/openbmc-test-automation#2105

Change-Id: Ie03b25ff88948bcccb09e9d82f8da86e28c92697
Signed-off-by: George Keishing <gkeishin@in.ibm.com>

show more ...

Fix synaccess response code

Changes:
- Minor changes in the REST response code checking

Tested:
robot -v OPENBMC_HOST:xx.xx.xx.xx -v PDU_IP:yy.yy.yy.yy
-v PDU_USERNAME:admin -v P

Fix synaccess response code

Changes:
- Minor changes in the REST response code checking

Tested:
robot -v OPENBMC_HOST:xx.xx.xx.xx -v PDU_IP:yy.yy.yy.yy
-v PDU_USERNAME:admin -v PDU_PASSWORD:*********
-v PDU_TYPE:synaccess -v PDU_SLOT_NO:1
redfish/extended/test_power_restore.robot

With this changes also, it is not fully working in our env.
This is more of a response changes fix for existing PDU.

Change-Id: I8ca64044d614329fb98291cad3c820d0a9a9b0d7
Signed-off-by: George Keishing <gkeishin@in.ibm.com>

show more ...

Enforced robotframework standards.

- The standards are enforced using the rflint static anylysis tool.
- More standards will be added in future commits but this is a base
starting

Enforced robotframework standards.

- The standards are enforced using the rflint static anylysis tool.
- More standards will be added in future commits but this is a base
starting point.

Change-Id: I7dd8a2b0b42a51327b748cb730609d7ee2538de3
Signed-off-by: Joy Onyerikwu <onyekachukwu.joy.onyerikwu@ibm.com>

show more ...

Check return code when doing PDU reset

PDU (Power Distribution Unit) will return HTTP_OK if successful.

Resolves openbmc/openbmc-test-automation#971
Change-Id: I153d9019ba3170fb

Check return code when doing PDU reset

PDU (Power Distribution Unit) will return HTTP_OK if successful.

Resolves openbmc/openbmc-test-automation#971
Change-Id: I153d9019ba3170fbb97522dc3ddd458cc4481a2b
Signed-off-by: Steven Sombar <ssombar@us.ibm.com>

show more ...

Add "SSHLibrary." qualifier to "Open Connection" invocation.

This failed when called by obmc_boot_test.robot.

Change-Id: I0b1a803a476ba0676675035e3110c8d9a0bea8e3
Signed-off-by:

Add "SSHLibrary." qualifier to "Open Connection" invocation.

This failed when called by obmc_boot_test.robot.

Change-Id: I0b1a803a476ba0676675035e3110c8d9a0bea8e3
Signed-off-by: Michael Walsh <micwalsh@us.ibm.com>

show more ...

Port suite from mkumatag personal repo w/o history

All these files came from https://github.com/mkumatag/openbmc-automation
The decision to remove the commit history was because most of

Port suite from mkumatag personal repo w/o history

All these files came from https://github.com/mkumatag/openbmc-automation
The decision to remove the commit history was because most of the 122
commits did not follow commit comment AND content best practices.
The ability to remove the commit history was possible because all
contributors where from the same company (IBM) making the coordination /
notification/acceptence easy. See all the gory details about the
first try to commit with history here...
https://github.com/openbmc/openbmc-test-automation/pull/1

This suite of tests will run against an OpenBMC based server. It will
run good/bad path testing against the REST interface. There are tests
that will also run ipmitool on the victim BMC too.

If you want to support a new system in to the suite you should only
have to edit two files...
data/<system>.py
tox.ini

The README.md contains details on how to setup for the first time along
with how to execute the test suite

NOTE: some test cases require tools that do not exist on the system.
Currently the ipmitool is needed and if you do not manually copy / link
it in to the tools directory some suites will fail.

show more ...