During a brief chat on IRC the following came up:
A next logical step after testing is integrated for issue queues would be to integrate tests into d.o.'s nightly build process.

The purpose for making this issue is simply to place the idea on the roadmap.

Things to consider when the time comes:
Tests need not stop a build (i.e. a failed test should not keep the build from happening or the package from being created), but it would be helpful if the results were published and/or included in the package.
It may be useful to include the tests themselves in the nightly build (or any release for that matter) so that people could conceivably run the same tests for themselves.

Comments

boombatower’s picture

Project: Test driven development infrastructure » Project issue file test
Version: » 6.x-2.x-dev

I think this would be nice to have, but part of this needs to be developed for PIFR as well.

boombatower’s picture

boombatower’s picture

Status: Postponed » Active

This should now be possible due to the major abstraction PIFR 2.x now has. This should be relatively simple to add now.

To confirm we are referring to testing branches (nightly releases).

boombatower’s picture

Title: Integrate tests into the nightly build process » Request test of nightly releases and display results
Component: Miscellaneous » Code
Assigned: Unassigned » boombatower
boombatower’s picture

Status: Active » Fixed

Currently code run per commit.

Should be more than sufficient...later it can provide a setting to choose.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.