It seems to me that instrumentation testing is integration testing with the ability to control the life cycle and the events (onStart, onCreate etc) of the app. Unit testing, as i understand it, is testing a Unit (eg Class) for its data and behavior. For example, say you have a game: this game runs on … Read more
This page may help, it reviews quite a few C++ unit test frameworks: CppUnit Boost.Test CppUnitLite NanoCppUnit Unit++ CxxTest Check out CPPUnitLite or CPPUnitLite2. CPPUnitLite was created by Michael Feathers, who originally ported Java’s JUnit to C++ as CPPUnit (CPPUnit tries mimic the development model of JUnit – but C++ lacks Java’s features [e.g. reflection] … Read more
You mention that you’re already using -x. The variable PS4 denotes the value is the prompt printed before the command line is echoed when the -x option is set and defaults to : followed by space. You can change PS4 to emit the LINENO (The line number in the script or shell function currently executing). … Read more
Lettuce means to be a cucumber-like tool for python: http://lettuce.it/ You can grab the source at github.com/gabrielfalcao/lettuce
You should be able to specify HTTP headers as the third argument to your get() method as described here: http://api.rubyonrails.org/classes/ActionDispatch/Integration/RequestHelpers.html#method-i-get and here http://api.rubyonrails.org/classes/ActionDispatch/Integration/Session.html#method-i-process So, you can try something like this: get ‘/my/path’, nil, {‘HTTP_ACCEPT’ => “application/json”}
Martin Fowler wrote an excellent article on this subject. From that article: Meszaros uses the term Test Double as the generic term for any kind of pretend object used in place of a real object for testing purposes. The name comes from the notion of a Stunt Double in movies. (One of his aims was … Read more
What Ruby on Rails TDD 101 article should I read? I will start with a guide to testing rails applications. Also Railscast has some excellent screencasts about how to use different testing tools. What do I need to test? I will start with models, since they are easy to test. The simple rule is that … Read more
This is now supported (since ScalaTest 2.1.3) within interactive mode: testOnly *MySuite — -z foo to run only the tests whose name includes the substring “foo”. For exact match rather than substring, use -t instead of -z. If you run it from the command line, it should be as single argument to sbt: sbt ‘testOnly … Read more
This should run all tests in current directory and all of its subdirectories: $ go test ./… This should run all tests for given specific directories: $ go test ./tests/… ./unit-tests/… ./my-packages/… This should run all tests with import path prefixed with foo/: $ go test foo/… This should run all tests import path prefixed … Read more
No this is not supported. We feel this is not needed, because in your regular CI runs you only care if the test passed or failed, and you see the details in the log. Also note that you can simulate this if you really want using a Scenario Outline: https://stackoverflow.com/a/54108755/143475 Finally, if you care so … Read more