Testers 3.2.2: what changed
Revision 1 to 2. Removed lines have a minus sign; added lines have a plus sign.
| Old | New | Line | |
|---|---|---|---|
| 1 | 1 | Anybody willing to contribute FPC and help to increase release quality by participating in systematic testing of release candidates and short checking of the final release. Note that this testing differs at least partly from just using the particular build for your own purposes, because you are supposed to perform a minimum set of defined operations, let us know when the testing is finished and report your results in certain time period (usually not more than one week - exact dates are provided when the builds are available). | |
| 2 | 2 | ||
| 3 | 3 | To test a release at least do the following. If some part is not available for the specific target you can skip it offcourse | |
| 4 | 4 | ||
| 5 | - | ||
| 6 | - | ||
| 7 | - | ||
| 8 | - | ||
| 9 | - | ||
| 10 | - | ||
| 11 | - | ||
| 12 | - | ||
| 13 | - | ||
| 14 | - | ||
| 15 | - | ||
| 16 | - | ||
| 17 | - | ||
| 18 | - | ||
| 19 | - | ||
| 20 | - | ||
| 21 | - | ||
| 22 | - | ||
| 5 | + | ```text | |
| 6 | + | Install the release (check that the version-numbers are correct) | |
| 7 | + | make sure readme.txt & whatsnew.txt are for the current version | |
| 8 | + | Read updated text files as distributed in release zip files | |
| 9 | + | readme.txt | |
| 10 | + | faq.txt | |
| 11 | + | whatsnew.txt | |
| 12 | + | run all distributed executables (in bin/*) | |
| 13 | + | open the installed hello.pp in IDE | |
| 14 | + | make a minor change in the demo in IDE & save it | |
| 15 | + | compile the demo file in IDE | |
| 16 | + | run the demo within the IDE (debugger) | |
| 17 | + | view documentation in IDE, traverse 2-3 pages (at least one with screenshots) | |
| 18 | + | make cycle with newly installed binaries and sources | |
| 19 | + | run testsuite | |
| 20 | + | Check PDF documentation (open all files) | |
| 21 | + | Check HTML documentation, if any | |
| 22 | + | Check TXT documentation, if any | |
| 23 | + | Check CHM documentation, if any | |
| 24 | + | ``` | |
| 23 | 25 | ||
| 24 | 26 | Instructions for the make cycle and testsuite are on the [[How to start]] page. Compare testsuite results against results from the previous published release; any new failures are regressions that should be reported. | |
| 25 | 27 | ||
| 26 | 28 | Report any findings on the [[Issues 3.2.2|issues]] page name and e-mail (account at domain) CPU - operating system - version/distribution RC1 testing status (how many percents done, when expected to finish) RC2 testing status First Last, somebody at some.domain Intel Septium HyperSuperSomething - Linux - SuSE 23.1 100% 95% (unable to finish XYZ due to lack of time) | |
| 27 | 29 | ||
| 28 | 30 | ## Candidates for testing of 3.2.2 | |
| 29 | 31 | ||
| 30 | 32 | Anybody willing to contribute FPC and help to increase release quality by participating in systematic testing of release candidates and short checking of the final release. Note that this testing differs at least partly from just using the particular build for your own purposes, because you are supposed to perform a minimum set of defined operations, let us know when the testing is finished and report your results in certain time period (usually not more than one week - exact dates are provided when the builds are available). | |
| 31 | 33 | ||
| 32 | 34 | To test a release at least do the following. If some part is not available for the specific target you can skip it offcourse | |
| 33 | 35 | ||
| 34 | 36 | 1. Install the release (check that the version-numbers are correct) | |
| 35 | 37 | 2. make sure readme.txt & whatsnew.txt are for the current version | |
| 36 | 38 | 3. Read updated text files as distributed in release zip files | |
| 37 | 39 | 1. readme.txt | |
| 38 | 40 | 2. faq.txt | |
| 39 | 41 | 3. whatsnew.txt | |
| 40 | 42 | 4. run all distributed executables (in bin/*) | |
| 41 | 43 | 5. open the installed hello.pp in IDE | |
| 42 | 44 | 6. make a minor change in the demo in IDE & save it | |
| 43 | 45 | 7. compile the demo file in IDE | |
| 44 | 46 | 8. run the demo within the IDE (debugger) | |
| 45 | 47 | 9. view documentation in IDE, traverse 2-3 pages (at least one with screenshots) | |
| 46 | 48 | 10. make cycle with newly installed binaries and sources | |
| 47 | 49 | 11. run testsuite | |
| 48 | 50 | 12. Check PDF documentation (open all files) | |
| 49 | 51 | 13. Check HTML documentation, if any | |
| 50 | 52 | 14. Check TXT documentation, if any | |
| 51 | 53 | 15. Check CHM documentation, if any | |
| 52 | 54 | ||
| 53 | 55 | Report any findings on the [[Issues 3.2.2]] page. | |
| 54 | 56 | ||
| 55 | 57 | | name and e-mail (account at domain) | CPU - operating system - version/distribution | RC1 testing status (how many percents done, when expected to finish) | RC2 testing status | | |
| 56 | 58 | |----|----|----|----| | |
| 57 | 59 | | First Last, somebody at some.domain | Intel Septium HyperSuperSomething - Linux - SuSE 23.1 | 100% | 95% (unable to finish XYZ due to lack of time) | | |
| 58 | 60 | | Karl-Michael.Schindler (at) web.de | MacBook Pro (Core i5) - macOS 11.2.3 | building x86_64-darwin and numerous cross compilers from sources, 100% | to be done | | |
| 59 | 61 | | Kirinn (at) mooncore.eu | Core i3-2328M - Linux - Arch 5.11.11 | 100% | | | |
| 60 | 62 | | Kirinn (at) mooncore.eu | Core i5-4590S - Windows 7 32-bit in QEMU VM | 100% | | | |
| 61 | 63 | | Kirinn (at) mooncore.eu | AMD R5 1500X - Windows 10 Home - 64-bit 20H2 | 100% | \|--} | | |
| 62 | 64 | ||
| 63 | 65 | --- | |
| 64 | 66 | *From the Free Pascal wiki, page "Testers 3.2.2", as it stood on 2021-04-03 after a change by Kirinn, out of the wiki's dump of 2024-05-26. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).* | |
| 65 | 67 | Category: FPC Testers |