Skip to content

Fix for thrown errors never invoking complete - #2

Open
johntimothybailey wants to merge 2 commits into
mxriverlynn:masterfrom
johntimothybailey:master
Open

Fix for thrown errors never invoking complete #2
johntimothybailey wants to merge 2 commits into
mxriverlynn:masterfrom
johntimothybailey:master

Conversation

@johntimothybailey

Copy link
Copy Markdown

In default Jasmine, when an error is thrown within a it() the tests will continue forward.
If an error occurs within the block function provided, then the complete function is never invoked and thus the tests will not move forward until the timeout is triggered (default: 2000). Let me know if you guys need a sample. This solved our issues with several hundred tests taking "forever" on failures.

…lve the complete (invoke complete). This solves an issue where a thrown error will never trigger the complete function.
…o the block function. This allows the developer to reference the spec within the block. With the Jasmine it function, the block supplied gets the context of spec (or rather is the context of spec)
@mkuklis

mkuklis commented Feb 27, 2013

Copy link
Copy Markdown

I ran into the same issue. Please merge this pull request :)

  block.call(this,complete);

fixes the problem.

@meleyal

meleyal commented Jun 14, 2013

Copy link
Copy Markdown

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants