ng-state
  • Introduction
  • Main differences
  • Getting Started
    • Instalation
    • Examples
  • Core concepts
    • Main idea
      • More complex flow visualization
    • Configuration
      • Immer Setup
      • ImmutableJs Setup
    • Store
      • Operators
      • Optimistic updates plugin
      • Optimistic updates plugin
      • Form manager plugin
        • onChange hook
        • shouldUpdateState hook
        • Custom form elements
      • Persist state plugin
        • Configuring custom storage
    • Actions
      • Immer
      • ImmutaleJs
      • Injectable Actions
    • Components with Actions
      • Signal Actions
      • State Actions
    • @InjectStore decorator
    • @WithStore decorator
    • @ComponentState decorator
    • Dispatcher
  • Different scenarios
    • Passing list item index via router
    • ngOnChanges hook
    • FormManager pitfalls
  • Unit testing
    • Setup
    • Test store
    • Test actions
    • Test component with actions
    • Test with Angular TestBed
  • Debugging
    • Setup
    • Redux DevTools
    • Automated changes output
    • Manual state changes check
    • Additional debugging information
  • Production
    • Production mode
    • Server Side Rendering (SSR)
  • Other information
    • Best practices
    • CLI
      • Custom Configurations
    • Performance
    • Blog Posts
    • Contributing
Powered by GitBook
On this page

Was this helpful?

  1. Unit testing

Test actions

Actions can be tested by calling NgStateTestBed.createActions method. createActions has required param actions and two params with default values: initialState with value {} and statePath with value []. This means that for most of situations we can pass just actions type and test application in localized state. But for more complex scenarios we can pass initial state and path.

it('should return actions', () => {
    const initialState = { todos: [] };
    initialState.todos.push({ description: 'test description' });

    const actions = NgStateTestBed.createActions<TestActions>(TestActions); // in this case actions will be created with state = {};
    // OR
    const actions = NgStateTestBed.createActions(TestActions, initialState, ['todos', 0]);
    // OR
    const actions = NgStateTestBed.createSignalActions(TestActions, initialState, ['todos', 0]);
    expect(actions.todoDescription).toEqual('test description');
});

where

  • first param is initialState is object or class

  • second param is statePath to bind actions to

  • third param is actions class

createActions as well as createSignalActions takes into consideration injectable actions. Dependenices are mocked and injected according to Angular TestBed.

PreviousTest storeNextTest component with actions

Last updated 8 months ago

Was this helpful?