I can invoke mvn cobertura:cobertura to instrument, run unit tests (using surefire), and generate reports.
I can invoke mvn verify to run unit tests and integration tests (using the failsafe Maven plugin).
But how do I call Maven to instrument, run unit tests and integration tests, and generate reports? The answer to Running integration tests with Cobertura Maven plugin did not work for me, and also I would not want to call verify with every Cobertura run, but only for nightly coverage.
You can try Jacoco and got on fly instrumentation with more flexible configuration for gathering of coverage and reporting
Not sure if I fully understand the question, but I always do a mvn site ...
Related
According to...:
https://learn.microsoft.com/en-us/azure/devops/pipelines/test/review-continuous-test-results-after-build?view=vsts
...You should be able to view test results for in-progress (automated)tests during the test execution but my test results are not published until the whole test run is complete. What am i doing wrong here?
In my release definition i have the Visual Studio test task. The automated GUI tests is executed from the Azure DevOps testHub which trigger the release job, but as said, the test results will not update until all tests are completed. How can this be done?
Also, why are my tests shown as "Others" and not "Not executed"?
(Im using the "Test run" option in the Visual studio test task for "Select tests using".)
I guess you configured it wrong.
In docs it's said:
So what needs to be done is on your test task you should switch on parallel run:
But be careful with parallel running, it may require some work with your tests to make it possible.
I was wondering if anyone could recommend best practise for SBT builds using Bamboo. I see that is a Bamboo plugin for SBT however it is a) unsupported and b) isn't compatible with later versions of Bamboo. This combination would almost certainly be a blocker for us as using it could lead to a position where we couldn't take a Bamboo update (potentially fixing a security issue) because it would break all of our SBT builds.
Presumably you can just set up Bamboo to build SBT projects as a script task but I'm a bit worried about the experience here as it's not clear to me how things like failing tests and code coverage will be represented.
Is it possible to have a reasonably slick SBT and Bamboo setup without using the plugin or is Bamboo not a suitable CI system to use with SBT?
We do heavily rely on bamboo in our sbt workflows. The plugin works fine but the only benefit over a short inline script is the parsing of tests which is also available as another task.
We love having some portable build scripts in the projects which can be also used by bamboo.
So here is the starter guide:
have a good portable build script in your project (presumably bash script)
call this script in an inline script in bamboo (so you can do some other stuff as well, e.g. checkout submodules, choosing docker host, ...)
How can one set up qunit to run integration tests against a remote site? I've used ember-cli test runner which has qunit + testem built in to run interation tests locally in an ember-cli project. How it does this, is to load the entire ember app in the qunit container then run the tests which can be unit or integration tests. This approach is also good if I can't have a JRE dependancy.
I think it may be possible to be able to load fooDomain.com/somepath in an iframe and then run the tests against it.
Has anyone a workflow for this?
Trying to setup my integration flow and I have some tests that are quite destructive using the velocity-cucumber package.
First issue I find is that these tests are being run on the standard Meteor db. Which on localhost and dev is fine, but not so great for production. As far as I can tell the velocity-cucumber doesn't do anything with mirrors yet.
Because of this I have two cases where I need Meteor to launch in a specific way.
1) On the CI server I need for JUST the tests to run then exit (hopefully with the correct exit code).
2) On the production server I need Meteor to skip all tests and just launch.
Is this currently possible with Meteor command line arguments? I'm contemplating making demeteorize a part of the process, and then use standard node.js testing frameworks.
To run velocity tests and then exit, you can allegedly run meteor with the --test option:
meteor run --test
This isn't working for me, but that's what the documentation says it is supposed to do.
To disable velocity tests, run meteor with the environment variable VELOCITY set to 0. This will skip setting up the mirror, remove the red/green dot, etc.:
VELOCITY=0 meteor run
When developing a test I would like to be able to run a single Karma unit test only. Is there a way to run one test only from the command line using Karma, or perhaps configure a simple task in Grunt that runs one test only?
Assuming that you're using Karma with Jasmine, simply change one or more describe() calls to fdescribe() calls, or it() calls to fit() calls. Only the f-prefixed tests will be run. This is documented in the focused_specs.js file of the Jasmine documentation.
(In older versions of Jasmine, the 'focused' versions of describe and it were instead called ddescribe and iit; try them if you're on an old version and can't upgrade.)