We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sometimes if you need to run a lot of expectations, you want to know about all of the failures rather than just the first one.
Ruby's RSpec accomplishes this like so:
it "returns success response from stripe" do aggregate_failures "stripe response" do expect(refund.amount).to eq 100 expect(refund.status).to eq "succeeded" expect(refund.id).to start_with "re_" end end
Ruby has the blessing of lots of block contexts, but we could maybe mimic that feature like so:
aggregateFailures( "stripe response", function() expect( refund.amount ).to.equal( 100 ) expect( refund.status ).to.equal( "succeeded" ) expect( string.StartsWith( refund.id, "re_" ) ).to.beTrue() end )
No doubt a nightmare to implement in the current runner code (bump on #24)
The text was updated successfully, but these errors were encountered:
brandonsturgeon
No branches or pull requests
Sometimes if you need to run a lot of expectations, you want to know about all of the failures rather than just the first one.
Ruby's RSpec accomplishes this like so:
Ruby has the blessing of lots of block contexts, but we could maybe mimic that feature like so:
No doubt a nightmare to implement in the current runner code (bump on #24)
The text was updated successfully, but these errors were encountered: