Jasmine JavaScript Testing Framework Jasmine Test Suite Organization 3

Question 1

Where should shared test state variables typically be declared in a describe block?

Accepted Answer

At the top of the describe block, outside any it() or beforeEach()

Answer

Declaring variables at the describe scope lets beforeEach assign fresh values before each spec while keeping the variable accessible.

Question 2

What happens to a spec whose beforeEach throws an error?

Accepted Answer

The spec is marked as failed and afterEach still runs

Answer

Jasmine fails the associated spec when its beforeEach throws, but afterEach cleanup still executes to avoid leaving shared state dirty.

Question 3

Can afterEach() access variables that were modified inside the it() block that just ran?

Accepted Answer

Yes, because they share the describe block's closure scope

Answer

Variables declared at describe scope form a closure shared by it(), beforeEach(), and afterEach(), so mutations in it() are visible in afterEach().

Question 4

What is the main purpose of nesting describe blocks inside one another?

Accepted Answer

To organize related specs and share scoped setup/teardown

Answer

Nested describes allow related specs to share beforeEach/afterEach hooks while keeping unrelated specs separate.

Question 5

How does Jasmine report a spec created with xit() or by calling pending() inside it()?

Accepted Answer

As 'pending' in the results output

Answer

Jasmine tracks pending specs separately and reports them as 'pending' so developers know they exist but haven't been implemented.

Jasmine JavaScript Testing Framework Practice Test