# integration tests; make non\_destructive; specifying sudo password

**URL:** <https://forum.ansible.com/t/integration-tests-make-non-destructive-specifying-sudo-password/16749>\
**Category:** Ansible Developer\
**Created:** [November 11, 2014, 6:37pm UTC](https://forum.ansible.com/t/integration-tests-make-non-destructive-specifying-sudo-password/16749 "2014-11-11T18:37:10Z")\
**Posts on this page:** 5\
**Page:** 1

<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:** [November 11, 2014, 6:37pm UTC](https://forum.ansible.com/t/integration-tests-make-non-destructive-specifying-sudo-password/16749/1 "2014-11-11T18:37:10Z")

</div>

Hello,

How do I specify a sudo password for when I am running the integration tests?

Jon

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [November 11, 2014, 6:44pm UTC](https://forum.ansible.com/t/integration-tests-make-non-destructive-specifying-sudo-password/16749/2 "2014-11-11T18:44:10Z")

</div>

I will assume you are using ‘make’ to run the tests. In which case, something like:

TEST\_FLAGS=‘-K’ make all

The TEST\_FLAGS env var is where you would place any/all additional areas you want to pass on to ansible-playbook

---

<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:** [November 12, 2014, 9:09pm UTC](https://forum.ansible.com/t/integration-tests-make-non-destructive-specifying-sudo-password/16749/3 "2014-11-12T21:09:23Z")

</div>

Thanks, that got me started.

Of course I’d missed the ‘run as root’ instruction, but have been passing -vvvv and other bits in my TEST\_FLAGS env var now I know about it.

Up and running now though and debugging my way through integration tests for windows port of file module.

Jon

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [November 17, 2014, 9:45pm UTC](https://forum.ansible.com/t/integration-tests-make-non-destructive-specifying-sudo-password/16749/4 "2014-11-17T21:45:27Z")

</div>

Yeah, I suspect we’ll have the integration tests for a while - sometimes it’s quite neccessary to test modules, but in the future with the v2/ subtree work going on, it will be able to make it easier to unit test most of the application as well (mostly save modules).

---

<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:** [November 19, 2014, 1:06pm UTC](https://forum.ansible.com/t/integration-tests-make-non-destructive-specifying-sudo-password/16749/5 "2014-11-19T13:06:13Z")

</div>

Thanks. They are useful for seeing how things are done ‘in the small’ too.

I’m currently porting the copy file and template tests for windows versions, where possible - its great having some tests to aim for rather than having to create them from scratch.