Testing forms and user interactions in Angular - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the testing module needed for reactive forms.

Angular

import { ReactiveFormsModule } from '@angular/forms';
import { TestBed } from '@angular/core/testing';

TestBed.configureTestingModule({
  imports: [[1]]
});

Drag options to blanks, or click blank then click option'

AFormsModule

BReactiveFormsModule

CHttpClientModule

DRouterModule

Attempts:

3 left

💡 Hint

Common Mistakes

Importing FormsModule instead of ReactiveFormsModule

Forgetting to import any forms module

You need to import ReactiveFormsModule to test reactive forms in Angular.

2fill in blank

medium

Complete the code to create a form control with an initial empty value.

Angular

import { FormControl } from '@angular/forms';

const nameControl = new FormControl([1]);

Drag options to blanks, or click blank then click option'

A''

Bnull

Cundefined

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using null or undefined which can cause unexpected behavior

Using 0 which is a number, not a string

To start with an empty string value in a form control, use ''.

3fill in blank

hard

Fix the error in the test to simulate a user typing 'hello' into an input element.

Angular

const input = fixture.nativeElement.querySelector('input');
input.value = [1];
input.dispatchEvent(new Event('input'));
fixture.detectChanges();

Drag options to blanks, or click blank then click option'

A"hello"

Bhello

C'hello'

Dinput.value

Attempts:

3 left

💡 Hint

Common Mistakes

Assigning a variable name without quotes

Using double quotes inconsistently

The value assigned to input.value must be a string literal, so it needs quotes like 'hello'.

4fill in blank

hard

Fill both blanks to check if the form control is valid and touched after user interaction.

Angular

expect(component.form.get('email')?.[1]).toBeTruthy();
expect(component.form.get('email')?.[2]).toBeTruthy();

Drag options to blanks, or click blank then click option'

Avalid

Binvalid

Ctouched

Dpristine

Attempts:

3 left

💡 Hint

Common Mistakes

Checking for 'invalid' instead of 'valid'

Using 'pristine' which means untouched

After user input, the form control should be valid and touched.

5fill in blank

hard

Fill all three blanks to simulate a button click and verify the form submission method is called.

Angular

const button = fixture.nativeElement.querySelector('button');
button.[1]();

expect(component.[2]).toHaveBeenCalled();

fixture.detectChanges();
expect(component.form.[3]).toBeTruthy();

Drag options to blanks, or click blank then click option'

Aclick

BonSubmit

Cvalid

Dreset

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'reset' instead of 'click' for the button event

Checking 'reset' property on the form instead of 'valid'

Calling a wrong method name instead of 'onSubmit'

The button is clicked with click(), the onSubmit method should be called, and the form should be valid.

Practice

1. What is the primary purpose of testing forms in Angular applications?

easy

A. To improve the app's visual design

B. To ensure the app correctly handles user input and form validation

C. To speed up the app's loading time

D. To reduce the size of the app bundle

Solution

1. Step 1: Understand form testing goals

   Testing forms focuses on verifying that user inputs are handled correctly and validations work as expected.

2. Step 2: Differentiate from unrelated goals

   Visual design, loading speed, and bundle size are unrelated to form testing.

3. Final Answer:

   To ensure the app correctly handles user input and form validation -> Option B

4. Quick Check:

   Form testing = user input handling [OK]

Hint: Form tests check input handling and validation only [OK]

Common Mistakes:

• Confusing form testing with UI styling
• Thinking form tests improve app speed
• Assuming form tests reduce bundle size

2. Which Angular testing utility is commonly used to create a test environment for components with forms?

easy

A. TestBed

B. HttpClientTestingModule

C. RouterTestingModule

D. NgModule

Solution

1. Step 1: Identify Angular testing utilities

   TestBed is the main utility to configure and create a test environment for components, including those with forms.

2. Step 2: Exclude unrelated modules

   HttpClientTestingModule is for HTTP tests, RouterTestingModule for routing, and NgModule is a decorator, not a testing utility.

3. Final Answer:

   TestBed -> Option A

4. Quick Check:

   TestBed sets up component tests [OK]

Hint: Use TestBed to set up component tests with forms [OK]

Common Mistakes:

• Confusing TestBed with HTTP or routing modules
• Using NgModule instead of TestBed for testing
• Not importing TestBed in test files

3. Given this test snippet, what will be the value of component.form.value.name after simulating user input?

component.form.controls['name'].setValue('Alice');
fixture.detectChanges();

medium

A. undefined

B. '' (empty string)

C. null

D. 'Alice'

Solution

1. Step 1: Understand setValue effect on form control

   Calling setValue('Alice') sets the 'name' control's value to 'Alice'.

2. Step 2: Confirm form value after change detection

   After fixture.detectChanges(), the form reflects the updated value.

3. Final Answer:

   'Alice' -> Option D

4. Quick Check:

   setValue updates form control value [OK]

Hint: setValue changes form control value immediately [OK]

Common Mistakes:

• Assuming value stays undefined without submit
• Confusing setValue with patchValue
• Forgetting to call detectChanges

4. In this test code, what is the main issue causing the test to fail?

it('should update form on input', () => {
  const input = fixture.nativeElement.querySelector('input[name="email"]');
  input.value = '[e-mail]';
  // Missing event dispatch here
  fixture.detectChanges();
  expect(component.form.value.email).toBe('[e-mail]');
});

medium

A. fixture.detectChanges() is called too early

B. The selector for input is incorrect

C. The input event is not dispatched after changing input value

D. The form control name is misspelled

Solution

1. Step 1: Identify missing user interaction simulation

   After setting input.value, the input event must be dispatched to update Angular form bindings.

2. Step 2: Understand effect of missing event

   Without dispatching the event, Angular does not detect the change, so form value remains unchanged.

3. Final Answer:

   The input event is not dispatched after changing input value -> Option C

4. Quick Check:

   Dispatch input event to update form [OK]

Hint: Always dispatch input/change events after setting input values [OK]

Common Mistakes:

• Forgetting to dispatch input or change events
• Assuming detectChanges alone updates form
• Using wrong input selectors

5. You want to test a form submission that disables the submit button while processing and re-enables it after success. Which approach correctly tests this user interaction?

hard

A. Simulate form input, trigger submit event, check button disabled state before and after async operation

B. Only check if the submit button is disabled on component load

C. Call the submit method directly without simulating user input or events

D. Test the button's CSS class changes without triggering form submission

Solution

1. Step 1: Simulate realistic user actions

   Testing should simulate user input and submit event to trigger form submission logic.

2. Step 2: Verify button state changes during async process

   Check that the submit button disables during processing and re-enables after success to confirm correct interaction.

3. Final Answer:

   Simulate form input, trigger submit event, check button disabled state before and after async operation -> Option A

4. Quick Check:

   Test full user flow including async button state [OK]

Hint: Test full submit flow including button state changes [OK]

Common Mistakes:

• Testing button state only on load
• Skipping user input simulation
• Ignoring async operation effects