From Fedora Project Wiki
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=A brief description of the functionality being tested. | |description=A brief description of the functionality being tested. | ||
{{admon/note|Note for kernel earlier 3.10|Before suspend need killall udevd in container}} | |||
|setup= | |setup= | ||
# Install: {{command|su -c 'yum install vzctl'}} | # Install: {{command|su -c 'yum install vzctl'}} | ||
Line 14: | Line 15: | ||
# Exit from container: {{command | logout}} | # Exit from container: {{command | logout}} | ||
# Suspend container: {{command | vzctl suspend 101}} | # Suspend container: {{command | vzctl suspend 101}} | ||
# Restore container: {{command | vzctl restore 101}} | # Restore container: {{command | vzctl restore 101}} or {{command | vzctl resume 101}} | ||
# Stop container: {{command | vzctl stop 101}} | |||
|results= | |results= | ||
The following must be true to consider this a successful test run. Be brief ... but explicit. | The following must be true to consider this a successful test run. Be brief ... but explicit. | ||
# | # All steps completes without error | ||
# | # Steps #3, #5 shows the same: | ||
<code> | |||
|optional=Optionally provide hints for exploratory testing. | |optional=Optionally provide hints for exploratory testing. | ||
}} | }} |
Revision as of 15:06, 9 July 2013
Description
A brief description of the functionality being tested.
Setup
- Install:
su -c 'yum install vzctl'
- Open terminal
- Switch to root user:
su -
How to test
- Create new container:
vzctl create 101 --ostemplate centos-6-x86_64
- Start container:
vzctl start 101
- Exec ps in container:
vzctl exec 101 ps axf
- Enter to container:
vzctl enter 101
- Exec ps in container directly:
ps axf
- Exit from container:
logout
- Suspend container:
vzctl suspend 101
- Restore container:
vzctl restore 101
orvzctl resume 101
- Stop container:
vzctl stop 101
Expected Results
The following must be true to consider this a successful test run. Be brief ... but explicit.
- All steps completes without error
- Steps #3, #5 shows the same:
Optional
Optionally provide hints for exploratory testing.