Travis-CI runs the test on a Linux box and I think it could also run on OSX, but I never tried that. Appveyor on the other hand is a cloud-based Continuous Integration that runs your tests on MS Windows. (Actually I just saw an e-mail from them inviting me to try their Linux servers as well. For now let's stick to the Windows machines.)

The Markua parser should have no platform dependent part. So our could is expected to run on MS Windows as well. I only have an old Windows 7 at home and I'd avoid using it. Luckily Appveyor can provide the platform to test the code.

Enable Appveyor

Visit Appveyor, click on "Sign up for free". Here I've created my own account by typing in my name, e-mail address and a password.

Then I clicked on the "+ New Project" link, selected Github, I think back when I first did this I had to authenticate at GitHub at this point, but now it just lists all the project I have.

I searched for perl5-markua-parser and as I hovered over the name the "+ add" link appeared on the right hand side. Clicking that I told Appveyor to start monitoring the project.

Configure Appveyor

In order to tell Appveyor what to do you need to create a file called appveyor.yml or .appveyor.yml (with a leading dot). It needs to include some instructions installing Strawberry Perl, installing any prerequisites, and then running the tests with gmake test.

The full file can be seen here: .appveyor.yml. 

$ git add .appveyor.yml
$ git commit -m "add appveyor configuration file"
$ git push

commit

Once I pushed out the changes both Travis and Appveyor started to build the project. Coveralls was updated by Travis and we got an e-mail from Appveyor:

Appveyor success e-mail

To tell the truth this is the first project where I manage to get Appveyor succeed in the first attempt. In many cases the project did not even started to run. The success is probably due to the fact that the project itself is really simple. So if Appveyor fails for you don't worry. It might take some tweaking in the appveyor.yml and in your code till the tests starts to pass.

The link in the e-mail leads to the full report of the process: appveyor build report

Appveyor Badge

There is a canonical link to the latest report, but even there I could not see any recommendation on how to add an Appveyor badge to my project. Luckily I already have it in a few of my projects so I copied it from one of them, tweaked it to refer to the current project and added this to the README.md file: 

[![Build status](https://ci.appveyor.com/api/projects/status/github/szabgab/perl5-markua-parser?svg=true)](https://ci.appveyor.com/project/szabgab/perl5-markua-parser/branch/master)

The new file is this: examples/markua-parser/d370818/README.md

# Markua Parser
[![Build Status](https://travis-ci.org/szabgab/perl5-markua-parser.svg?branch=master)](https://travis-ci.org/szabgab/perl5-markua-parser)
[![Coverage Status](https://coveralls.io/repos/github/szabgab/perl5-markua-parser/badge.svg?branch=master)](https://coveralls.io/github/szabgab/perl5-markua-parser?branch=master)
[![Build status](https://ci.appveyor.com/api/projects/status/github/szabgab/perl5-markua-parser?svg=true)](https://ci.appveyor.com/project/szabgab/perl5-markua-parser/branch/master)

[Markua](https://leanpub.com/markua/) is a Markdown-inspired format to write books.

This module implements parsing (part of) the Markua specification.

Then the usual: 

$ git add .
$ git commit -m "add Appveyor badge"
$ git push

commit

If you visit the project now perl5-markua-parser and scroll down where the content of the README.md is displayed then you will see the badges. (By the time you visit it, you might see additional badges. So don't be surprised.

Now that we have enabled Continuous Integration both on Linux and on Windows, and we also monitor our test coverage we can proceed with the actual code.