TeamCity can be configured to invoke your test suite upon commit.
The following steps will help us prep are TeamCity to run our test suite when the code changes are committed:
- Set up TeamCity like the previous recipe, and have it started up. You also need to have
gitinstalled, as mentioned earlier in this chapter. - Create an empty folder for this recipe.
gturnquist$ mkdir /tmp/recipe49 - Initialize the folder for source code maintenance.
gturnquist$ git init /tmp/recipe49 Initialized empty Git repository in /private/tmp/recipe49/.git/
- Copy the shopping cart application into the folder, add it, and commit the changes.
gturnquist$ cp cart.py /tmp/recipe49/ gturnquist$ cd /tmp/recipe49/ gturnquist$ git add cart.py gturnquist$ git commit -m "Added shopping cart application to setup this recipe." [master (root-commit) 057d936] Added shopping cart application to setup this recipe. 1 files changed, 35 insertions(+), 0 deletions(-) create mode 100644 cart.py
These steps will show us how to create a TeamCity job that polls version control to detect a change and then run a test suite.
- Login to TeamCity console.
- Underneath Projects tab, click Create project.
- Type in recipe49, and then click Create.
- Click Add a build configuration for this project.
- Enter nose testing for the name and then click VCS settings.
- Click on Create and attach new VCS root.
- Enter recipe49 in VCS root name.
- Select Git as the Type of VCS.
- Enter
/tmp/recipe49as the Fetch URL. - Click on Test Connection to confirm settings and then click Save.
- Click on Add Build Step.
- Select Command Line for Runner type.
- Select Custom script for Run type and enter the following script:
. /Users/gturnquist/ptc/bin/activate nosetests tests.py
You must replace this with the command to activate your own virtualenv and invoke nosetests.
- Click on Save.
- Click on Build Triggering.
- Click on Add New Trigger.
- Pick VCS Trigger from Trigger Type.
- At the top, it should display VCS Trigger will add build to the queue if VCS check-in is detected. Click Save.
- Navigate back to Projects. There should be no jobs scheduled or results displayed.
- Click on Run. It should fail, because we haven't added the tests to the repository.
- From the command line, copy the test file into the repository. Then add it and commit it.
gturnquist$ cp tests.py /tmp/recipe49/ gturnquist$ cd /tmp/recipe49/ gturnquist$ git add tests.py gturnquist$ git commit -m "Adding tests." [master 4c3c418] Adding tests. 1 files changed, 20 insertions(+), 0 deletions(-) create mode 100644 tests.py
- Go back to the browser. It may take a minute for TeamCity to detect the change in the code and start another build job. It should automatically update the screen.
In this recipe, we configured TeamCity to do a job for us tied to a specific trigger. The trigger is: whenever a check in is done to the software baseline. We had to take several steps to configure this, but it demonstrates the flexible power TeamCity offers.
We also installed the teamcity-nose plugin, which gave us more details on the results.
TeamCity calls our nose testing job a build job. That is because running tests isn't the only thing TeamCity is used for. Instead, it's geared to build packages, deploy to sites, and any other action we may want it to do anytime a commit happens. This is why CI servers are sometimes called build servers.
But if we start with simple jobs like testing the baseline, we are well on our way to discovering the other useful features TeamCity has to offer.