pear:qa:ci
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| pear:qa:ci [2011/08/25 15:08] – [How to test a new PEAR release] CVS -> SVN danielc | pear:qa:ci [2012/04/12 23:13] – [My unit tests need a (database/server/setup/configuration)] clockwerx | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| * [[http:// | * [[http:// | ||
| * [[http:// | * [[http:// | ||
| - | * [[http:// | + | * [[http:// |
| * [[https:// | * [[https:// | ||
| - | The helper scripts live at http://svn.php.net/ | + | The helper scripts live at https://github.com/ |
| - | ===== Cruise Control | + | ===== Jenkins |
| - | Cruise Control | + | Jenkins |
| - | + | ||
| - | The build task does: | + | |
| - | - Update svn | + | |
| - | - Run '' | + | |
| - | - Run '' | + | |
| - | - Run '' | + | |
| - | - Run '' | + | |
| - | - Run '' | + | |
| - | - Build the package with Pyrus '' | + | |
| - | + | ||
| - | If either the unit tests or building the package fails, the build is marked as a failure. | + | |
| - | + | ||
| - | A file, called trunk.tar.gz is created as a build artifact. | + | |
| ==== How do I make sure my tests work? ==== | ==== How do I make sure my tests work? ==== | ||
| Line 37: | Line 24: | ||
| ... or as per the phpunit command above. | ... or as per the phpunit command above. | ||
| + | |||
| + | http:// | ||
| ==== My directory layout doesn' | ==== My directory layout doesn' | ||
| Line 55: | Line 44: | ||
| $ pear run-tests -r tests/ | $ pear run-tests -r tests/ | ||
| $ phpunit tests/ | $ phpunit tests/ | ||
| - | $ phpunit tests/ | ||
| # Commit | # Commit | ||
| Line 69: | Line 57: | ||
| - Checking your environment and skipping the test if it cannot run | - Checking your environment and skipping the test if it cannot run | ||
| + | There is also a test mysql instance available. | ||
| + | |||
| + | > Hi Daniel: | ||
| + | > | ||
| + | > On Wed, Nov 16, 2011 at 08:34:04AM +1030, Daniel O' | ||
| + | > > http:// | ||
| + | > > | ||
| + | > > This and a few others obviously need a database to be tested properly. | ||
| + | > > Certainly that machine has mysql on it; or sqlite is probably available - | ||
| + | > > what would be needed to load up an appropriate schema/tear it down after | ||
| + | > > the tests? | ||
| + | > | ||
| + | > I agree and mentioned this on pear-qa a while ago. Take a look at what | ||
| + | > I committed to DB tests yesterday. | ||
| + | > MYSQL_TEST_* environment variables, which are used for PHP's tests. | ||
| + | > should create a test user and database and set those environment | ||
| + | > variables in the cron job, or whatever. | ||
| + | > | ||
| + | > A similar setup should be made for PostgreSQL in PEAR and PHP's unit | ||
| + | > tests. | ||
| + | > | ||
| + | > SQLite3 tests should use ": | ||
| + | > | ||
| + | > Thanks, | ||
| + | > | ||
| + | > --Dan | ||
| ==== Todo ==== | ==== Todo ==== | ||
| - | - Fix how pear2-packages-all and pear2/all relate to the test suite | + | - Put more packages |
| - | - Generate a changelog, package.xml file (possibly in pearweb, possible on the command line) automatically; | + | |
| - | - Investigate what's up with the Metrics and other Cruise Control errors | + | |
| - Investigate a notification task to package maintainers? | - Investigate a notification task to package maintainers? | ||
| - Investigate allowing bootstrapped build.xml files back in (Pyrus) | - Investigate allowing bootstrapped build.xml files back in (Pyrus) | ||
| Line 89: | Line 101: | ||
| pear upgrade -f PEAR | pear upgrade -f PEAR | ||
| pear upgrade XML_RPC | pear upgrade XML_RPC | ||
| - | svn co http://svn.php.net/ | + | git clone git://github.com/ |
| cd pear-core/ | cd pear-core/ | ||
| </ | </ | ||
pear/qa/ci.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1