Search Results for "expect"

...One thing to note, is that superagent now sends any HTTP error (anything other than a 2XX response code) to the callback as the first argument if you do not add a status code expect (i.e. .expect(302)). Expectations are run in the order of definition. This characteristic can be used to modify the response body or headers before executing an assertion.

...If you’re upgrading from version 2.x or below, read the rspec-rails upgrade notes to find out what to watch out for. In RSpec, assertions are called expectations, and every expectation is built around a matcher. When you expect(a).to eq(b), you’re using the eq matcher. RSpec Rails defines ten different types of specs for testing different parts of a typical Rails application. Each one inherits from one of Rails’ built-in TestCase classes, meaning the helper methods provided by default in Rails tests are available.

...It then adds all the test steps to a test scenario. Then the default() main function is inserted. If you compile, link and execute the Sample, you will have an idea of what you should expect when you have finished writing your test.

TUT performs all required tasks that one can expect from unit test framework, but at the same time is small and robust (about 2.5k SLOC with 98% self-test coverage). Deploying TUT is very fast, since it is a header-only library.