courtly
courtly
courtly
courtly

Upcoming Events

San Francisco CiviCRM Meetup - February 8th, 2012
February 8th, 2012
Come meet others from the Bay Area who are interested in, using or developing (more...)

UK usergroup - London meetup
February 8th, 2012
Come and meet others from the UK that are using CiviCRM or are interested in (more...)

Chicago CiviCRM Meetup
February 17th, 2012
Please join other CiviCRM users, administrators, and developers in the Chicago (more...)

London user and administrator training
February 23rd, 2012
A comprehensive two day hands on training course covering the configuration, (more...)

CiviCRM London sprint Feb 2012
February 27th, 2012
Following the CiviCRM training here in London, we will have a CiviCRM code (more...)

Philadelphia - CiviCRM Meetup for Q1 2012
March 13th, 2012

UK South West - CiviCRM Meetup
March 20th, 2012
Come meet others from the Area who are interested in, using or developing for (more...)

[Bristol, UK] user and administrator training
March 21st, 2012
A comprehensive hands on training course covering the configuration, (more...)

San Francisco user and administrator training
March 29th, 2012
A comprehensive two day hands on training course covering the configuration, (more...)

CiviCRM Usability, Test and Code Sprint - San Francisco (March 2012)
March 29th, 2012
This usability, code and test sprint is targeted at CiviCRM users and (more...)

CiviCon 2012 San Francisco Bay Area - April 2nd 2012
April 2nd, 2012
CiviCon is THE annual event bringing together the people who use, develop, (more...)

CiviCRM Documentation, Test and Code Sprint - after CiviCon San Francisco (April 2012)
April 4th, 2012
This sprint is targeted at CiviCRM users and developers who want to work on (more...)

CiviCRM Components

Tools for engaging your supporters...

CiviContribute

CiviEvent

CiviMail

CiviMember

CiviReport

CiviCRM testing infrastructure

Not Just a Contact Database

These optional components give you more power to connect and engage your supporters.

  • civiCASE

  • Case management for clients and constituents.

  • civiEVENT

  • Online event registration and participant tracking.

  • civiMEMBER

  • Online signup and membership management.

  • civiMAIL

  • Personalized email blasts and newsletters.

  • civiREPORT

  • Report generation and template management.

October 1, 2009 - 04:30 — michal

Not a well known fact until now - during 3.0 release cycle, we've been working hard with DharmaTech to start regularly using unit tests for CiviCRM development and quality assurance. It's time to go out of the closet, since we're nearing the end of the first stage of this project - which was setting up everyone in the team with proper tools and migrating all the tests that we wrote before to our new framework.

So here's what we have right now:

  • A list of tests that we have right now is here http://tests.dev.civicrm.org/results/ It's not fully green (meaning - some tests still fail), since we're still in the process of migrating old tests and fixing them, but we hope to get to "all green" state soon. This page is being regenerated every 30 minutes (for now) and we'll be using it to continually check for regression bugs.
  • Code coverage report is here http://tests.dev.civicrm.org/coverage/ - we are doing quite good with API tests especially, coverage has been increasing steadily in last weeks. This should make our API more stable and reliable for integrators to work with.

Once we're finally done with current stage (finishing the migration), next steps will be:

  1. Starting to run tests against 3.0 (stable) code and for trunk (3.1 development) in the same time. This way, we'll see the regression happening on the trunk as new features jump in and will be able to wipe out some of the newly introduced problems long before alpha testing.
  2. Work on increasing the coverage for existing tests - the goal for 3.1 is API tests code coverage at 80% (at 59% currently), BAO tests code coverage at 50% (at 43% right now).
  3. Introducing browser tests (aka web tests). We'll be using Selenium and PHPUnit for this and hope for significant time savings on quality assurance we run before each stable release.

I'll be writing about this more, but will start with short request now: if you're using CiviCRM, filing issues and fixing bugs, please consider also helping us out with our unit tests. Filing an issue which has a test case attached speeds up fixing the bug considerably and also ensures that the similar bugs gets wiped out in the future in case they show up again during development of new versions. For now, if you want to get started, here are the instructions on how to set up the unit testing sandbox for CiviCRM.

( categories: )