Difference between revisions of "Testers 3.2.0"

From Free Pascal wiki
m (Candidates for testing of 3.2.0: Fixed typo)
(Add results for Fedora 31)
 
(11 intermediate revisions by 4 users not shown)
Line 2: Line 2:
  
 
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).
 
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).
 +
 +
* Downloads are available at the main FTP server: ftp://ftp.freepascal.org/pub/fpc/beta/3.2.0-rc1/
 +
* For an overview of what is new, see [[FPC New Features 3.2]]
 +
* For changes that may break backwards compatibility, see [[User Changes 3.2]]
 +
 +
== Release Testing Procedure ==
  
 
To test a release at least do the following. If some part is not available for the specific target you can skip it of course.  
 
To test a release at least do the following. If some part is not available for the specific target you can skip it of course.  
  
 
# Install the release (check that the version-numbers are correct)
 
# Install the release (check that the version-numbers are correct)
# make sure readme.txt & whatsnew.txt are for the current version
+
# Make sure readme.txt & whatsnew.txt are for the current version
 
#  Read updated text files as distributed in release zip files
 
#  Read updated text files as distributed in release zip files
 
## readme.txt
 
## readme.txt
 
## faq.txt
 
## faq.txt
 
## whatsnew.txt
 
## whatsnew.txt
# run all distributed executables (in bin/*)
+
# Run all distributed executables (in bin/*)
# open the installed hello.pp in IDE
+
# Open the installed hello.pp in the FPC text mode IDE
# make a minor change in the demo in IDE & save it
+
# Make a minor change in the demo in the FPC text mode IDE & save it
# compile the demo file in IDE
+
# Compile the demo file in the FPC text mode IDE
# run the demo within the IDE (debugger)
+
# Run the demo within the FPC text mode IDE (debugger)
# view documentation in IDE, traverse 2-3 pages (at least one with screenshots)
+
# View documentation in the FPC text mode IDE, traverse 2-3 pages (at least one with screenshots)
# make cycle with newly installed binaries and sources
+
# Make cycle with newly installed binaries and sources
# run testsuite
+
# Run test suite (source package download needed for fpsrc/tests)
 
# Check PDF documentation (open all files)
 
# Check PDF documentation (open all files)
 
# Check HTML documentation, if any
 
# Check HTML documentation, if any
Line 30: Line 36:
 
| First Last, somebody at some.domain || Intel Septium HyperSuperSomething - Linux - SuSE 23.1 || 100% || 95% (unable to finish XYZ due to lack of time)
 
| First Last, somebody at some.domain || Intel Septium HyperSuperSomething - Linux - SuSE 23.1 || 100% || 95% (unable to finish XYZ due to lack of time)
 
|-
 
|-
| karl-michael.schindler@web.de || Intel Core i5 - macOS - 10.14 || to be expected until 06-04-2019||  
+
| karl-michael.schindler@web.de || Intel Core i5 - macOS - 10.15 || 100% minor [[Issues_3.2.0|issues]] reported||
 +
|-
 +
| lazarus [=at=] sentry.org || Intel Core i7 (6 core with hyperthreading) - macOS - 10.15.4 || 100% (IDE n/a for macOS); [[Issues_3.2.0|issues]] reported ||
 +
|-
 +
| dbannon [-@-] internode.on.net || Ubuntu 20.04 beta, 1st April ;-) in Virtual Box || All Good, very minor [[Issues_3.2.0|issues]] reported. Note I also built Lazarus trunk in both Qt5 and GTK2 version. The GTK2 version has problems (slow to start, crash at exit) but as the QT5 one works as expected and the GTK2 version shows same problem with FPC304, the issue is Lazarus, not FPC.||
 +
|-
 +
| kirinn [-@-] mooncore.eu || i5 4590s - Windows 7 32-bit (Qemu VM) || 100%. Minor [[Issues_3.2.0|issues]] reported, nothing platform-specific I think. The test suite completed successfully but had 8 bad compilations and 12 failed runs.||
 +
|-
 +
| kirinn [-@-] mooncore.eu || i5 4590s - Fedora 31 64-bit (Qemu VM) || 100% No platform-specific issues noticed. The test suite completed successfully but had 13 bad compilations and 12 failed runs.||
 
|--}
 
|--}
  
 
[[Category:FPC Testers]]
 
[[Category:FPC Testers]]

Latest revision as of 23:43, 17 May 2020

Candidates for testing of 3.2.0

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).

Release Testing Procedure

To test a release at least do the following. If some part is not available for the specific target you can skip it of course.

  1. Install the release (check that the version-numbers are correct)
  2. Make sure readme.txt & whatsnew.txt are for the current version
  3. Read updated text files as distributed in release zip files
    1. readme.txt
    2. faq.txt
    3. whatsnew.txt
  4. Run all distributed executables (in bin/*)
  5. Open the installed hello.pp in the FPC text mode IDE
  6. Make a minor change in the demo in the FPC text mode IDE & save it
  7. Compile the demo file in the FPC text mode IDE
  8. Run the demo within the FPC text mode IDE (debugger)
  9. View documentation in the FPC text mode IDE, traverse 2-3 pages (at least one with screenshots)
  10. Make cycle with newly installed binaries and sources
  11. Run test suite (source package download needed for fpsrc/tests)
  12. Check PDF documentation (open all files)
  13. Check HTML documentation, if any
  14. Check TXT documentation, if any
  15. Check CHM documentation, if any

Report any findings on the 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)
karl-michael.schindler@web.de Intel Core i5 - macOS - 10.15 100% minor issues reported
lazarus [=at=] sentry.org Intel Core i7 (6 core with hyperthreading) - macOS - 10.15.4 100% (IDE n/a for macOS); issues reported
dbannon [-@-] internode.on.net Ubuntu 20.04 beta, 1st April ;-) in Virtual Box All Good, very minor issues reported. Note I also built Lazarus trunk in both Qt5 and GTK2 version. The GTK2 version has problems (slow to start, crash at exit) but as the QT5 one works as expected and the GTK2 version shows same problem with FPC304, the issue is Lazarus, not FPC.
kirinn [-@-] mooncore.eu i5 4590s - Windows 7 32-bit (Qemu VM) 100%. Minor issues reported, nothing platform-specific I think. The test suite completed successfully but had 8 bad compilations and 12 failed runs.
kirinn [-@-] mooncore.eu i5 4590s - Fedora 31 64-bit (Qemu VM) 100% No platform-specific issues noticed. The test suite completed successfully but had 13 bad compilations and 12 failed runs.