Qt563 release testing
Please add your name when starting to test certain package so others are aware whom to ask or share findings.
Put OK (tester_name), if the package seems to be OK, or NOK (tester_name), if not. Remember to use bugreports.qt.io for bug reporting! You can also add bug ID in addition to name/OK/NOK.
Due to build process reasons installers are from different builds with different build number for Linux, Mac and Windows platforms. If build content for those platform is same then build identifiers are on same column.
| Platform | Version # | ||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 5.6.3Snapshot
Linux:# MacOS:# Windows:# | |||||||||||||||||||||||||||||||||||||||||||
| Linux x64 | |||||||||||||||||||||||||||||||||||||||||||
| Android on Linux x64 | |||||||||||||||||||||||||||||||||||||||||||
| macOS | |||||||||||||||||||||||||||||||||||||||||||
| Android on macOS | |||||||||||||||||||||||||||||||||||||||||||
| iOS | |||||||||||||||||||||||||||||||||||||||||||
| Android on Windows | |||||||||||||||||||||||||||||||||||||||||||
| MinGW | |||||||||||||||||||||||||||||||||||||||||||
| MSVC 2013 x86 | |||||||||||||||||||||||||||||||||||||||||||
| MSVC 2013 x64 | |||||||||||||||||||||||||||||||||||||||||||
| MSVC 2015 x86 | |||||||||||||||||||||||||||||||||||||||||||
| MSVC 2015 x64 | |||||||||||||||||||||||||||||||||||||||||||
| WinRT on MSVC2013 | |||||||||||||||||||||||||||||||||||||||||||
| WinRT on MSVC2015 |
} Fresh, completely new online installation always provides latest available Beta \ RC release version. When updating existing installation both Installed version and New version information is available via MaintenanceTool (behind "Update components" selection, see details from How to get snapshot via online installer). Build id tracked on release testing should equal to "Qt 5.10" Component Name version info (other submodules may have slightly different build id due to build process). Testing scopeThis section is work in progress and has not been agreed upon yet. Can be used if seen beneficial. The goal is to define a minimal subset of examples that the tester has to go through and confirm it is in working order. It is not the intention to prevent the tester from randomly going through other examples but it ensures that major areas are covered on every platform. The predefined test set should not require more than 30 mins.
|