Editing Test writer
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 7: | Line 7: | ||
* [[Guide to writing Manual tests|Guide to writing Manual tests]] | * [[Guide to writing Manual tests|Guide to writing Manual tests]] | ||
* [[Manual testing plans|Manual testing plans]] | * [[Manual testing plans|Manual testing plans]] | ||
| + | |||
== Writing Automated Tests == | == Writing Automated Tests == | ||
| Line 12: | Line 13: | ||
As the name suggests, automated tests are tests that are automatically ran against software. | As the name suggests, automated tests are tests that are automatically ran against software. | ||
They also report any errors found during the tests automatically. We prefer tests written in the Python programming language. | They also report any errors found during the tests automatically. We prefer tests written in the Python programming language. | ||
| + | |||
| + | {{FIXME|add tests from all OpenVZ components}} | ||
If you have strong knowledge in C then you may contribute to these tests: | If you have strong knowledge in C then you may contribute to these tests: | ||
| − | * [https://github.com/xemul/criu/tree/master/test CRIU (Checkpoint and Restore in Userspace)] | + | * [https://github.com/xemul/criu/tree/master/test CRIU (Checkpoint and Restore in Userspace) autotests] |
| − | * [https://github.com/xemul/p.haul/tree/master/test | + | * [https://github.com/xemul/p.haul/tree/master/test p.haul autotests] |
| − | * [https://github.com/xemul/libct/tree/master/test | + | * [https://github.com/xemul/libct/tree/master/test libct autotests] |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category: QA]] | [[Category: QA]] | ||
