Dotcover report (nunit) is not covering all the classes in the assembly. When I see the report generated by Dotcover using nunit-console.exe (2.4.1), I find only couple of classes from the assembly but not all.
I don’t use NUnit with dotCover, but there are the common things.
Did you check your dotCover config file? Probably, there are some filters there.
More info here: http://www.jetbrains.com/dotcover/webhelp/dotCover__Introducing_Console_Runner.html
Related
My project is composed of several DLLs that I must test with different unit tests. I generate an XML file for each of the tests then I transform them into a JUnit format to be read by Jenkins. It works very well.
On the other hand, the test results are all in the same topic on the Jenkins interface and I would like to separate them for each DLL. It is for a more practical aspect for the visualization of the tests. I haven't found the solution yet. That's why I'm asking you if there is a solution for this problem.
I tried several plugins like JUnit or Warning NG. But the result remains the same. The JUnit plugin puts all the results in the same section and makes no distinction and the Warning NG plugin fails to parse the XML report to display it in Jenkins.
I have a set of test cases, for which I need to demonstrate an analysis. Is there a plugin or any other way to analyse test results?
You can use Cobertura Maven Plugin for analysing and code coverage reports on the unit tests.
You can refer the below links for more details on Cobertura Maven Plugin:
http://www.mojohaus.org/cobertura-maven-plugin/
https://www.mkyong.com/qa/maven-cobertura-code-coverage-example/
For Netbeans, you can refer tikione-jacocoverage plugin from below link:
http://plugins.netbeans.org/plugin/48570/tikione-jacocoverage
I want to run all the ignored tests in my solution in a different build configuration in TeamCity.
I didn't see any explicit why to do it in the build step configuration page.
Can it be done?
The Ignore attribute is the wrong thing to use here. It should be used for tests you do not wish to run at all. Try using Categories instead. TeamCity has two properties you can set within an NUnit build step.
NUnit categories include and NUnit categories exclude control which tests will be run.
How did you mark your tests - your question is not quite clear in this point? Did you use the Explicit or Ignored attribute? If the latter then these tests will not run at all.
I am using VC++ 2005 and 2008 on a project. Now I want to see if the unit test cases cover all the code, and a found a problem. We use Boost.Test for unit testing, and each file is designed to test a particular function or method. Each file is compiled into a separate executable.
I am able to view the results per executable in Visual Studio. What I am really interested in is to view the overall code coverage by all the tests combined. Is there a way to combine the code coverage results?
I don't know about Visual Studio's test coverage tools.
Our SD C++ Test Coverage Tool will combine test coverage vectors from a single instrumented set of source code, no matter how many times you compile/link it (as long as you don't change the source of the code being tested). This tool can be obtained for the Visual Studio dialect(s) of C++. SD's test coverage tools for other languages have this same property.
C++ Coverage Validator can combine results from different code coverage sessions. You can combine sessions interactively using the GUI or from the command line (so you can automate things).
Alternatively you could set up the automatic merging to a central session and get every code coverage session automatically merged into the central session.
I'm generating clover coverage reports (using Clover's maven plugin), and I'd like to exclude a certain package from the coverage reports (specifically, because it's UI code that intentionally isn't covered by my unit tests, but the reason doesn't really matter.)
I can see how to exclude that package from being instrumented (using in the plugin configuration), but I can't see how to exclude it from the report. The intended solution appears to be to use a Context; however, there is no package-level context available (only block, method, and statement.)
As far as I know, excluding classes from instrumentation should exclude them from the report as well. Answers to the question #9 of this thread seem to confirm this:
9) Are their independent options for filtering at both the instrumentation level and at the reporting level?
Yes. The clover-setup takes a fileset of files to instrument. All clover-report tasks also take a fileset of sources to report coverage on. The clover-maven2-plugin provides includes/excludes at instrumentation time and full Ant fileset support for filtering at report time. Ant filesets give you all the power of fileset selectors to determine which files to include/exclude.
Could you try to do a full clean build (delete all previously compiled classes and all files in the Clover DB) to ensure that previously instrumented versions of your UI classes are removed and check again.
If this doesn't work, please run you build with the debug option (mvn -X > output.txt) and attach the output and your pom.xml to this question.