I often do that with UI-tests as it is annoying to write code while they run :D
still no fun
@JohanLarsson - yeah, there's a few challenges here - stop writing slow tests being a priority
Made screen recordings and grabbed the time from there
should script it
nunit has always been faster than xunit when I have benchmarked
but that's not based on any real evidence
But reverted after first testrun
The r# runner is much faster than the vs runner now
The vs runner does not run the tests at all many times
Just shows the blue spinner things for a couple of minutes
do you use moq?
Do you use a container in the tests?
@cristobalito If you read this comment https://github.com/nunit/nunit3-vs-adapter/issues/487#issuecomment-389209491 they [JetBrains] say they are using the adapter for .net core. As they have their own testhost they have full control over what they send to the adapter. The adapter itself are aware of the explicit, but doesn't do anything really with it, so if they pass it down through the RunTest method for test cases, it will be run, and they can handle the removal of the same too.
Anyone interested in an opensource project?
Spec oriented development speeds up programming by generating code based on tests/specs. Tests required will be the same or less specs as a normal developer writes.
https://github.com/Neur0plasticity/spec-dev
MSG me if interested
From what I found if I want to pass in a Dictionary I have to wrap that in a static IEnumerable<object[]> and pass that by calling [TestCaseSource(nameof(method))].
Is that the only way? I ask because in the very next test I need that data again but I also need an int. If I add an int to that object[] then the first test will fail because it expects that int to be passed.
This is what I have setup so far: https://gist.github.com/Programazing/181a28607fb924f9368a6d68a12a88ea
or can I somehow pick which
object[] to use for which test?
I also realize this could be a totally wrong way to approach this. I just found that on a random SO answer the other night.
@Programazing I'm not sure what you are trying to obtain, but if you want to use the same dictionary in multiple tests, then you can do something like (note that you don't need to use
[Theory] and that most of these attributes are for providing multi testcases to a test a not just one testcase). The code below will create one test that gets the string and the dictionary and another test that will have 3 test cases - each testcase will consist of a number (from 1 to 3) and the dictionary.using NUnit.Framework;
using System.Collections.Generic;
[TestFixture]
public class BigramTests
{
[Test]
public void Create_ReturnsCorrect_NumberOfBrigams(
[Values("The quick brown fox and the quick blue hare")] string input,
[ValueSource(nameof(Create_ReturnsCorrect_NumberOfBrigams_TestData))] Dictionary<string, int> actual)
{
...
}
[Test]
public void Create_ReturnsCorrect_NumberOfBrigams(
[Values(1, 2, 3)] int input,
[ValueSource(nameof(Create_ReturnsCorrect_NumberOfBrigams_TestData))] Dictionary<string, int> actual)
{
...
}
static IEnumerable<Dictionary<string, int>> Create_ReturnsCorrect_NumberOfBrigams_TestData()
{
var bigram = new Dictionary<string, int>()
{
{ "the quick", 2 },
{ "quick brown", 1 },
{ "brown fox", 1 },
{ "fox and", 1 },
{ "and the", 1 },
{ "quick blue", 1 },
{ "blue hare", 1 }
};
return new[] { bigram };
}
}
You can read more about the different attributes at https://github.com/nunit/docs/wiki/Attributes
@mmaist Assume you mean the adapter. I want to get it out soon, but would like some more feedback on it. There are 19 downloads so far of the pre-release, no one have been screaming so it might be working as it should. However, there are 3 issues which it doesn't fix, but which it was expected to fix. If you have the possibility to give it a quick spin on your build, it would be awesome
For anyone else wanting to give it a try, grab the pre-release here: https://www.myget.org/feed/nunit/package/nuget/NUnit3TestAdapter
