# Current status of handling skipped tests when using gradle/TestNG

**URL:** https://discuss.gradle.org/t/current-status-of-handling-skipped-tests-when-using-gradle-testng/13599
**Category:** Help/Discuss
**Created:** [January 8, 2016, 4:33pm UTC](https://discuss.gradle.org/t/current-status-of-handling-skipped-tests-when-using-gradle-testng/13599 "2016-01-08T16:33:25Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Robert\_Kruger](https://avatars.discourse-cdn.com/v4/letter/r/f07891/32.png) [@Robert\_Kruger](https://discuss.gradle.org/u/Robert_Kruger)
#### Post date: [January 8, 2016, 4:33pm UTC](https://discuss.gradle.org/t/current-status-of-handling-skipped-tests-when-using-gradle-testng/13599/1 "2016-01-08T16:33:25Z")

</div>

I ran into a similar problem as described in a very old forum post:

> [@Is there a way to configure build to fail on skipped tests when using testng?](https://discuss.gradle.org/t/is-there-a-way-to-configure-build-to-fail-on-skipped-tests-when-using-testng/2107):
>
> I’m working on porting a maven build I have, and I’m running into problems in the test phase when running testng tests. As a background, my TestNG tests all extend spring-test’s AbstractTransactionalTestNGSpringContextTests, which means there are some inherited @Before tags which are responsible for reading my spring application context from bean files and dynamically injecting needed beans into my Test class before executing any of the tests. Turns out I misconfigured my test resources to poi…

Bottom line is, I want to have a way to make tests fail if an unhandled exception occurs in TestNG data providers. How things currently seem to behave, this does not happen causing tests not to run without anyone noticing for weeks. More details in: [Redirecting to Google Groups](https://groups.google.com/forum/#!topic/testng-users/E6WNR_rt-n0)

What are my odds to solve this on the gradle level? Any suggestions?