release.json 4.0 KB
Newer Older
1 2 3 4 5
{
    "name": "Release Test Plan",
    "description": "Test Plan to be performed before a release is cut",

    "tests": [
C
Cleber Rosa 已提交
6 7 8 9

        {"name": "Check status of master branch",
         "description": "Navigate to:\n\n   https://github.com/avocado-framework/avocado#build-and-quality-status\n\nand make sure that all build and quality services report good indicators"},

10
	{"name": "Avocado source is sound",
11
	 "description": "On your development machine, on a freshen Avocado source to be released, run `$ make check-full`. Expected result: Make command should say OK."},
12

13 14 15
	{"name": "Avocado source does not contain spelling errors",
	 "description": "On your development machine, on a freshen Avocado source to be released, run `$ make spell`. Expected result: Make command should say OK."},

16
	{"name": "Avocado RPM install",
17 18 19
	 "description": "On a fresh virtual machine, install Avocado using its COPR repo.  Run:\n- dnf -y copr enable @avocado/avocado-latest\n- dnf -y install python-avocado-* python2-avocado-* python3-avocado-* qemu-guest-agent rpmlint\n- systemctl start qemu-guest-agent\n- systemctl enable qemu-guest-agent"},

        {"name": "Avocado RPM lint",
20
        "description": "On the same machine you just installed Avocado, check if there are packaging errors by running: `$ rpmlint python*-avocado*`.  Expected result: XX packages and 0 spec files checked; 0 errors, YY warnings."},
21

22
	{"name": "Avocado Test Run on RPM based installation",
23
	 "description": "On the same machine you just installed Avocado used during RPM packages ('Avocado RPM install'), run the simplest possible test with `$ avocado run passtest.py`. Expected results: `(1/1) passtest.py: PASS (0.00 s)`. After the test, shutdown the virtual machine."},
24 25

	{"name": "Avocado Test Run on Virtual Machine",
26
	 "description": "On your development machine, execute Avocado with the Virtual Machine plugin, so that a test will be run on the machine you just installed Avocado using RPM packages. Run: `$ avocado run passtest.py --vm-domain <domain> --vm-username <user> --vm-password <pass>`. Expected results: `(1/1) /home/<user>/(...)/passtest.py: PASS (0.00 s)`"},
27 28

	{"name": "Avocado Test Run on Remote Machine",
29
	 "description": "On your development machine, execute Avocado with the Remote plugin, so that a test will be run on the machine you just installed Avocado using RPM packages. Run: `$ avocado run passtest.py --remote-username <user> --remote-password <pass> --remote-hostname <host> --html /tmp/report.html`. Expected results: `(1/1) /home/<user>/(...)/passtest.py: PASS (0.00 s)`"},
30 31

	{"name": "Avocado Remote Machine HTML report",
32
	 "description": "On a web browser, open the previously generated  HTML report at `/tmp/report.html`. Verify that all the links such as `job-YYYY-MM-DD...` (under `Results Dir`), `1-/**/avocado/tests/**/examples/tests/passtest.py:PassTest.test` (under `Test ID`) and `debug.log` point to valid locations."},
33

34 35
	{"name": "Avocado VT",
	 "description": "Configure avocado vt as described in http://avocado-vt.readthedocs.org/en/latest/GetStartedGuide.html including the `avocado list` and running the migration test. Expected result: No errors."},
36

37
	{"name": "Avocado HTML report sysinfo",
38
	 "description": "On the HTML report, click on `Sysinfo (pre/post/profile, click to expand)` and verify that system information such as `hostname` and `cpuinfo` are present and accurate"},
39 40

	{"name": "Avocado HTML report links",
41
	 "description": "On the HTML report, verify that all the links such as `job-YYYY-MM-DD...` (under `Results Dir`), `1-type_specific.io-github-autotest-qemu.migrate.default.tcp` (under `Test ID`) and `debug.log` point to valid locations."},
42 43 44

	{"name": "Paginator",
	"description": "Start new terminal and store the stty setting by running `stty -a > /tmp/tty_state_pre`. Then run `AVOCADO_LOG_EARLY=y avocado config` and verify paginator is enabled, colored output is produced and quit. Then run `stty -a > /tmp/tty_state_post` followed by `diff /tmp/tty_state_{pre,post}` and verify the setting was not changed (no output)."}
45

46 47
    ]
}