Opened 11 years ago

Closed 9 years ago

#27 closed TODO (General task list) (fixed)

Automated testing infrastructure

Reported by: David Sommerseth Owned by: Samuli Seppänen
Priority: major Milestone: beta 2.3
Component: Community services Version:
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:
Cc:

Description

Setup a testing infrastructure based on Beaker.

Change History (7)

comment:1 Changed 11 years ago by Samuli Seppänen

Status: newaccepted

comment:2 Changed 10 years ago by Samuli Seppänen

Beaker may be an overkill. There is now t_client.sh integration in buildslaves, which is a kind of "mini-Beaker" environment. In practice, buildslave try to connect using 4 different configuration files to a remote servers after each build. This should catch most obvious issues easily.

comment:3 Changed 10 years ago by Samuli Seppänen

Milestone: beta 2.3

comment:4 Changed 10 years ago by Samuli Seppänen

Component: Generic / unclassifiedCommunity services

comment:5 Changed 10 years ago by Samuli Seppänen

Testing Trac ticket submit button on Opera.

comment:6 Changed 10 years ago by Samuli Seppänen

When the public test server was taken offline, we obviously lost the t_client.sh integration in our buildslaves. So, before or soon after 2.3 alpha release ensure that

  • Upgrade buildbot to latest stable release
  • The new public test server is configured
  • Add t_client.sh rules to buildmaster's master.cfg

comment:7 Changed 9 years ago by David Sommerseth

Resolution: fixed
Status: acceptedclosed

We now have a working testing infrastructure based on t_client.sh which buildbots makes use of. In addition some of the developers have also this access directly. Closing this one as fixed.

Note: See TracTickets for help on using tickets.