I have a vb.net project that runs nunit tests. I am struggling to even build this project right as it keeps giving the following error 'Type ' ' not defined. Any idea how to configure the teamcity to build and run scripts from project.
Maybe some code isn't checked in properly, and TeamCity can't build because of that. Try to do a fresh checkout from your repository to a new folder, and build the project/solution there.
When the project builds, then we can look into getting it to test with NUnit.
Related
Yesterday created folder "integration" through Visual Studio Code and added my tests in it, but Cypress do not see them. Then, moved tests to already exists folder "2-advanced-examples" and tests run fine.
Today I started Visual Studio Code and I see my tests in folder "2-advanced-examples" but missing them in same folder when start Cypress. Cypress removed my tests by unknown reason.
Any ideas about correct way to add my tests without to be removed again?
*Added screenshot from VSC and Cypress.
What I did for resolving: Restart Cypress, re-added tests to folder "2-advanced-examples".
Expected Cypress to display my tests.
I am trying to set up a Java project in Eclipse which uses Gradle for its builds plus some self-defined Groovy code for the builds (placed - as usual - under buildSrc).
So I first created a Java project from the existing code and then additionally assigned the "Gradle nature" to the project. Since then I keep getting this error message:
Could not run phased build action using Gradle installation 'C:\opt\gradle-5.4.1'.
Execution failed for task ':buildSrc:compileGroovy'.
Compilation failed; see the compiler error output for details.
What is this message trying to tell me???
This issue was raised several times in the past. To solve it:
Delete all the files in the .gradle directory in your project and under your username, e.g.:
C:\Users\username\.gradle
Restart your computer.
Run Eclipse as administrator.
Build the project.
Finally, if you have any script which runs Gradle in addition to the installation /distribution of Gradle that Eclipse knows - do NOT use the script. It seems to confuse Eclipse regarding the location of Gradle.
I'm a Cucumber and Eclipse beginner and have a few questions and hope you can help me to get through this: I created a sample cucumber test scenario, a sample test steps and a cucumber runner. The scenarios runs fine within eclipse IDE (Neon). I used Maven as the dependency manager. I also installed the Maven command line module. The step code is Java.
Here is the (basic) question: How do I create a jar file from my cucumber test scenario so that execute it via command line so that I can bring the test scenario to Jenkins CI? Is there anything I need to do with Maven BEFORE I can build the jar file?
Thanks a lot folks!
If you run Cucumber using the JUnit runner, then all you have to do to run from a command line is to execute Maven and make sure you invoke a life cycle phase that includes running the unit tests. One way would be
mvn test
An example that might get you up and running can be found at
https://github.com/cucumber/cucumber-java-skeleton
In simple words: How to runs in eclipse tests with building process (as simple as possible)?
I want to execute test defined in pom with every maven build. Currently all is build, but none test is run. When I execute maven test it runs test, but during build it only builds.
How can I add this phase to eclipse build process?
I already read Eclipse Maven Build and Test with One Button, and it is close to optimal, still I would like to run tests with build to be more TDD.
My solution(might not be optimal):
require maven runpath
Go to Project -> Builders
Add new Program
In Edit configuration enter (as on picture):
Location: your/maven/path
arguments: test -f /yourProjectPomPath/pom.xml
As on picture tab Build Options -> Check(click) During auto builds option select
Save changes and check if all works
I'm trying to put together a Continuous Integration server that will do the following:
Work with subversion
Use NUnit tests (fail build on failed tests)
Use partcover (fail build on < X% coverage)
Run code against FxCop (fail build on FxCop warnings, given settings)
Run code against StyleCop (fail build on StyleCop warnings, given settings)
Not as important:
Be able to run from a sln file
Be able to publish the application (ClickOnce is setup for the project already)
I'm using TeamCity right now and it doesn't seem to do 3 or 5, and it doesn't have a runner for the newest NUnit.
From the list of plugins that hudson has, it looks like it can do all of these except 3 (and the not as important requests). I've considered writing a plugin for hudons to use partcover, but that's adding more time to setting up a build server.
NAnt can be used as a build script which will build your projects and then execute NUnit and FXCop.
Another option, which is what I use at work, is create a build script for MSBuild and use the MSBuild Community Tasks which support running FXCop & NUnit among other things.
So for my setup CCNet pulls down the source from SVN then calls MSBuild with the main build file. Inside there it builds the projects, runs NUnit, NCover, FXCop, StyleCop etc. and merges the results which are then displayed on the CCNet webpage. Each task can also be set so if there's a failure the build fails.
I haven't used TeamCity but there should be a way to pull down the source and then run an MSBuild or NAnt build script which will then handle the build steps.
It's not a continuous integration server if it's run from a sln file. Perhaps you're mixing build tool and continuous integration. Many CI servers today does nothing but run build scripts made for other tools like NAnt or Maven. Look at NAnt first if it's what you're looking for. NAnt is able to do the build and execute other tools like FXCop (using NAntContrib library). You use CI server to run a build script on a regular basis.