| #
9778eb2c |
| 30-Jun-2020 |
Marissa Garza <garzam@us.ibm.com> |
Updated FOR loop syntax to new robot version
Signed-off-by: Marissa Garza <garzam@us.ibm.com>
Change-Id: Id543440c04974e6cfa8adbb6e8100759cd903d82
|
| #
839a0c27 |
| 31-Jan-2019 |
Sandhya Somashekar <sansomas@in.ibm.com> |
Replace resource.txt with resource.robot
Change-Id: I4d2afd35645880e33a31644cd717bbeae55666f0
Signed-off-by: Sandhya Somashekar <sansomas@in.ibm.com>
|
| #
fb218a16 |
| 28-Nov-2018 |
George Keishing <gkeishin@in.ibm.com> |
Update code to adhere to coding guideline
Change-Id: I859340a2f17e19b7b5cbb24807499db7ad455f74
Signed-off-by: George Keishing <gkeishin@in.ibm.com>
|
| #
f4a807bf |
| 20-Jun-2018 |
Joy Onyerikwu <onyekachukwu.joy.onyerikwu@ibm.com> |
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 ...
|
| #
b29d2e84 |
| 07-Jun-2016 |
Chris Austen <austenc@us.ibm.com> |
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 ...
|