Initial base infrastructure support for open BMC FFDC

This change includes the following
- initial support struture for FFDC
- scp connection introduced

Resolves openb

Initial base infrastructure support for open BMC FFDC

This change includes the following
- initial support struture for FFDC
- scp connection introduced

Resolves openbmc/openbmc-test-automation#39

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

show more ...

Enable long run test with provided number of iteration

Resolves openbmc/openbmc-test-automation#46

Change-Id: I1cf53779534d1a5fe8ec9efc6f769d483e5f415c
Signed-off-by: Sivas SRR

Enable long run test with provided number of iteration

Resolves openbmc/openbmc-test-automation#46

Change-Id: I1cf53779534d1a5fe8ec9efc6f769d483e5f415c
Signed-off-by: Sivas SRR <sivas.srr@in.ibm.com>

show more ...

Support multiple users running robot tests

You can use robot with jenkins. What I saw was the argument file was
explictly written to /tmp. The Jenkins is a different user then my
u

Support multiple users running robot tests

You can use robot with jenkins. What I saw was the argument file was
explictly written to /tmp. The Jenkins is a different user then my
user id so when Jenkins owned the /tmp/argument_file.txt my user id
trying to do things manually got a file permission error... and
visa versa. So I am moving the argument_file.txt to a location
based off of the workspace where the test is being executed.
That allows multiple users on the same system to run the suite.

Change-Id: I81525c7f20708dbd24d219c8424cad59144ba4ab
Signed-off-by: Chris Austen <austenc@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 ...