# Testing by activating CI on your fork of Ansible?

**URL:** <https://forum.ansible.com/t/testing-by-activating-ci-on-your-fork-of-ansible/25123>\
**Category:** Ansible Developer\
**Created:** [July 28, 2017, 10:23pm UTC](https://forum.ansible.com/t/testing-by-activating-ci-on-your-fork-of-ansible/25123 "2017-07-28T22:23:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bob\_Tanner](https://avatars.discourse-cdn.com/v4/letter/b/49beb7/32.png) [@Bob\_Tanner](https://forum.ansible.com/u/Bob_Tanner)\
**Post date:** [July 28, 2017, 10:23pm UTC](https://forum.ansible.com/t/testing-by-activating-ci-on-your-fork-of-ansible/25123/1 "2017-07-28T22:23:44Z")

</div>

I’d like to run the tests on my fork of the Ansible project.

How do I do that?

The documentation is sparse and many broken links (I’ve opened issues on the broken links)

Ansible moved from TravisCI to Shippable?

If so, is the move complete?

I see I can get 150 builds on Shippable a month for free.

Does the Testing Working Group still exist?

[https://github.com/ansible/community/blob/master/MEETINGS.md](https://github.com/ansible/community/blob/master/MEETINGS.md) is a broken link

Thanks.

---

<div class="post-metadata">

**Author:** ![j.r.hawkesworth](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@j.r.hawkesworth](https://forum.ansible.com/u/j.r.hawkesworth)\
**Post date:** [August 3, 2017, 1:12pm UTC](https://forum.ansible.com/t/testing-by-activating-ci-on-your-fork-of-ansible/25123/2 "2017-08-03T13:12:26Z")

</div>

So I believe if you create a PR Shippable will run tests against it anyway, so in that sense you need only create a PR from your fork to make use of the existing CI tests.

Testing is not the only working group!

see [http://docs.ansible.com/ansible/latest/community.html#irc-meetings](http://docs.ansible.com/ansible/latest/community.html#irc-meetings) which links to [https://github.com/ansible/community/blob/master/meetings/README.md](https://github.com/ansible/community/blob/master/meetings/README.md) for details of current meetings.

If you have some hardware you can set up some inventory and use ‘ansible-test’ to do integration testing locally.

I thoroughly recommend taking a moment to set up argcomplete (and activating it for ansible-test). Lots of information about integration testing here: [http://docs.ansible.com/ansible/latest/dev\_guide/testing\_integration.html](http://docs.ansible.com/ansible/latest/dev_guide/testing_integration.html)

Hope this helps,

Jon

---

<div class="post-metadata">

**Author:** ![Andrew\_Latham](https://avatars.discourse-cdn.com/v4/letter/a/ed8c4c/32.png) [@Andrew\_Latham](https://forum.ansible.com/u/Andrew_Latham)\
**Post date:** [August 3, 2017, 1:16pm UTC](https://forum.ansible.com/t/testing-by-activating-ci-on-your-fork-of-ansible/25123/3 "2017-08-03T13:16:22Z")

</div>

I would suggest trying “”“make tests”“” and you can see how that works at [https://github.com/ansible/ansible/blob/devel/Makefile#L118-L128](https://github.com/ansible/ansible/blob/devel/Makefile#L118-L128) if you want.