[Solved] Identify the issue in this Angular test:describe('Promise test', () => { it('checks resolved value', () => { const promise = Promise.resolve(10); expect(promise).toBe(10); }); }); | Angular

Angular - Testing

Identify the issue in this Angular test:

describe('Promise test', () => { it('checks resolved value', () => { const promise = Promise.resolve(10); expect(promise).toBe(10); }); });

AThe test uses an invalid Jasmine matcher

BThe test correctly compares the resolved value of the promise

CThe test is missing the describe block

DThe test compares a Promise object directly to a number without awaiting it

Step-by-Step Solution

Solution:

Step 1: Understand Promise behavior
A Promise is an object and must be awaited or resolved to get its value.
Step 2: Analyze the test code
The test compares the Promise object directly to a number, which is incorrect.
Final Answer:
The test compares a Promise object directly to a number without awaiting it -> Option D
Quick Check:
Always await promises before assertions [OK]

Quick Trick: Never compare Promise object directly to values [OK]

Common Mistakes:

Master "Testing" in Angular

9 interactive learning modes - each teaches the same concept differently

More Angular Quizzes

Identify the issue in this Angular test: