Difference between revisions of "Testers 2.6.2"

From Free Pascal wiki
Jump to navigationJump to search
(Copy from 2.6.0)
 
(fix)
Line 1: Line 1:
Editing Testers 2.6.2 (section)
+
== Candidates for testing of 2.6.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).
  
Please note that all contributions to Free Pascal wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
+
To test a release at least do the following. If some part is not available for the specific target you can skip it offcourse
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Free Pascal wiki:Copyrights for details). Do not submit copyrighted work without permission!
+
 
Summary:
+
# Install the release (check that the version-numbers are correct)
This is a minor edit  Watch this page
+
# make sure readme.txt & whatsnew.txt are for the current version
    Cancel | Editing help (opens in new window)
+
#  Read updated text files as distributed in release zip files
page discussion edit history move watch
+
## readme.txt
Mischi my talk my preferences my watchlist my contributions log out
+
## faq.txt
navigation
+
## whatsnew.txt
Main Page
+
# run all distributed executables (in bin/*)
Documentation
+
# open the installed hello.pp in IDE
FAQ
+
# make a minor change in the demo in IDE & save it
Downloads
+
# compile the demo file in IDE
Glossary
+
# run the demo within the IDE (debugger)
Index
+
# view documentation in IDE, traverse 2-3 pages (at least one with screenshots)
Recent changes
+
# make cycle with newly installed binaries and sources
Random page
+
# run testsuite
Help
+
# Check PDF documentation (open all files)
search
+
# Check HTML documentation, if any
   
+
# Check TXT documentation, if any
toolbox
+
# Check CHM documentation, if any
What links here
+
Report any findings on the [[Issues x.x.x]|issues] page
Related changes
+
 
Upload file
+
{| border="1" cellspacing="0" cellpadding="4"
Special pages
+
! 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
+
|-
Privacy policy About Free Pascal wiki Disclaimers
+
| First Last, somebody at some.domain || Intel Septium HyperSuperSomething - Linux - SuSE 23.1 || 100% || 95% (unable to finish XYZ due to lack of time)
 +
|--}

Revision as of 21:29, 13 November 2012

Candidates for testing of 2.6.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).

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

  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 IDE
  6. make a minor change in the demo in IDE & save it
  7. compile the demo file in IDE
  8. run the demo within the IDE (debugger)
  9. view documentation in IDE, traverse 2-3 pages (at least one with screenshots)
  10. make cycle with newly installed binaries and sources
  11. run testsuite
  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 x.x.x]|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)