Our post-build tests are executed through a script task. When the tests are executed, status is displayed as "Building for 8 mins". It seems Bamboo categorically associates a script task to build. Is there a way to configure a script task as a test script task instead of build script task?
the following post describes a solution
"No tests found": how do I make bamboo aware of my custom tests?
our test application now produces a JUnit xml file which is consumed by a JUnit Parser 'final' task
No, I did not find a way. Our tests are still executing via script tasks. They are not recognized by Bamboo as tests.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John, did you find the way how to force bamboo to understand script task as test? We are facing the same problem, we have about 15 tests in script, but the results of each script task (test) is not shown in test results. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.