Error loading plugin include
ParseError: syntax error, unexpected 'include' (T_INCLUDE), expecting identifier (T_STRING) or '{'
More info is available in the error log.
ParseError: syntax error, unexpected 'include' (T_INCLUDE), expecting identifier (T_STRING) or '{'
More info is available in the error log.
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| qa:isotesting [2018/04/29 20:12] – no real changes, this is just a test knome | qa:isotesting [2018/05/10 19:35] (current) – flocculant | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== ISO Testing ===== | ===== ISO Testing ===== | ||
| - | |||
| - | ==== Milestones ==== | ||
| - | Not all testing cycles will use all the milestones available to us, though in general an LTS cycle will include them. | ||
| - | |||
| - | While Daily testing is an on-going requirement, | ||
| - | |||
| - | **NOTE: | ||
| - | |||
| - | ^ Release | ||
| - | |Alpha 1 (opt-in)| | | ||
| - | |Alpha 2 (opt-in)| | | ||
| - | |Beta 1 (opt-in)|Follows Feature Freeze/ | ||
| - | |Beta 2 |Follows UI and Documentation Freeze | | ||
| - | |Release Candidate |Week prior to Release | | ||
| - | |Final Release| | | ||
| - | |||
| - | Dates for milestones can be found on the current Release Schedule. | ||
| - | |||
| - | Milestones, including Daily, are listed on the [[http:// | ||
| - | |||
| - | {{milestones.png}} | ||
| ==== ISO Test Builds ==== | ==== ISO Test Builds ==== | ||
| - | Once you've visited the tracker and can see what builds | + | Test builds available for testing |
| This page will look similar to this | This page will look similar to this | ||
| Line 38: | Line 17: | ||
| {{downloads.png}} | {{downloads.png}} | ||
| - | If you are going to be regularly testing the iso, you might look at using [[https:// | + | If you are going to be regularly testing the iso, you might look at using [[https:// |
| This can make some difference in the amount to download, particularly useful if your speed is slow, spotty or you have download limits. | This can make some difference in the amount to download, particularly useful if your speed is slow, spotty or you have download limits. | ||
| Line 64: | Line 43: | ||
| If you have noted bugs during the testcase you have 2 options: | If you have noted bugs during the testcase you have 2 options: | ||
| - | Critical bugs: These are bugs which cause you to not pass the testcase. For example - you start the installer but are unable to complete. Mark your test as Failed.< | + | Critical bugs: These are bugs which cause you to not pass the testcase. For example - you start the installer but are unable to complete. Mark your test as Failed.< |
| Bugs: These are bugs discovered during the test, which don't affect the testcase. For example, an application not part of the test, crashes and you see the crash dialogue. | Bugs: These are bugs discovered during the test, which don't affect the testcase. For example, an application not part of the test, crashes and you see the crash dialogue. | ||
| Line 71: | Line 50: | ||
| ==== Notes ==== | ==== Notes ==== | ||
| - | < | ||
| - | |||
| - | alias image=' | ||
| - | <sup>2</ | + | <sup>1</ |
