unit testing - NUnit Test Runner and Visual Studio NUnit Test runner get different results for a test -

-

in the geometry library writing have strange test passes when run using nunit test runner in visual studio, when runs on regular nunit runner fails. testing same dlls

here test:

    [test()]     public void line_sort()     {         line line1 = new line(pointgenerator.makepointwithinches(3, 2, 5), pointgenerator.makepointwithinches(5, 3, 7)); //intersects @ -1, 0, 1         line line2 = new line(pointgenerator.makepointwithinches(6, 0, 0), pointgenerator.makepointwithinches(-5, 3, -1)); //intersects @ 6, 0, 0         line line3 = new line(pointgenerator.makepointwithinches(1, 1, 5), pointgenerator.makepointwithinches(2, 2, 4)); //intersects @ 0, 0, 6         line line4 = new line(pointgenerator.makepointwithinches(4, 10, 1), pointgenerator.makepointwithinches(4, 5, 2)); //intersects @ 4, 0, 3         line line5 = new line(pointgenerator.makepointwithinches(4, 2, 2), pointgenerator.makepointwithinches(4, 2, 1)); //doesnt intersect          list<line> lines = new list<line> { line2, line3, line5, line4, line1 };          lines.sort();          lines[0].should().be(line1);         lines[1].should().be(line3);         lines[2].should().be(line4);         lines[3].should().be(line2);         lines[4].should().be(line5);     }

it seems sort function works differently in 2 cases. causing test fail in nunit runner list order not equal expected.

enter image description here

enter image description here

what cause this? , how can fix it? our build server behaves same nunit runner


Comments

Post a Comment

Popular posts from this blog

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall...
Read more

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co...
Read more

java - UML - How would you draw a try catch in a sequence diagram? -

-
Image
is there standard way of drawing try catch sequence diagrams? i've made attempt based on this feel end result doesn't feel right. code diagram based around: public static void save () { try { filehandle filehandle = gdx.files.external(file); filehandle.writestring(boolean.tostring(constantshandler.soundenabled)+"\n", false); (int = 0; < 5; i++) { filehandle.writestring(integer.tostring(constantshandler.highscores[i])+"\n", true); } } catch (throwable e) { } } my attempt note: know still need add loop. that's ok. fragments meant show conditional control flow in sequence diagram. superstructures puts limitations on use of fragments (see pp. 467 of ss2.1.1). should use critical region try part above. , option catch . however, keep telling can take quite freedom in using uml. it's language , such changes in life time. long reader ge...
Read more