AngularJasmineKarmaDemo

This project was generated with Angular CLI version 12.1.3.

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Running unit tests

Run ng test to execute the unit tests via Karma. You can run the tests even without the server running 😲

About this project

It is intended to be an introduction to unit testing with jasmine, providing information on the most basic concepts and sample tests. This is a work in progress, so, content will be added whenever possible.

About Jasmine tests

Jasmine is a behavior-driven development framework for testing JavaScript code. It does not depend on any other JavaScript frameworks. It does not require a DOM. And it has a clean, obvious syntax so that you can easily write tests. It's developed by Pivotal Labs and is open-source.

Karma: is a test runner, it allows us to run the test suite. It's developed by Google.

Both, Jasmine and Karma, come preinstalled and preconfigured in an Angular project created with Angular CLI.

The Unit Tests must be coded in component-name.spec.ts files, so that Karma can find them.

There are a couple of example tests with comments on the item and add-item components.

Test doubles

Son un término genérico que hace referencia a cualquier caso en el que se reemplaza un objeto de producción con otro con el único objetivo de probar el código.

According with Gerard Meszaros there are at least 5 kinds of doubles https://en.wikipedia.org/wiki/Test_double

• Test stub: used for providing the tested code with "indirect input".
• Mock object: used for verifying "indirect output" of the tested code, by first defining the expectations before the tested code is executed.
• Test spy: used for verifying "indirect output" of the tested code, by asserting the expectations afterwards, without having defined the expectations before the tested code is executed. It helps in recording information about the indirect object created.
• Fake object: used as a simpler implementation, e.g. using an in-memory database in the tests instead of doing real database access.
• Dummy object: used when a parameter is needed for the tested method but without actually needing to use the parameter.

AAA Pattern: sections of a Unit Test

1. Arrange: code required to setup a specific test. Here objects would be created, mocks setup, ...

   fixture = TestBed.createComponent(AddItemComponent);
   component = fixture.componentInstance;

2. Act: which should be the invocation of the method being tested

   component.form.controls['name'].setValue('foo');
   component.form.controls['description'].setValue('bar');
   component.form.controls['price'].setValue('33');

3. Assert: check whether the expectations were met.

   expect(component.form.valid).toBeTruthy();

Jasmine assertion functions

• expect(array).toContain(member);
• expect(fn).toThrow(string);
• expect(fn).toThrowError(string);
• expect(instance).toBe(instance);
• expect(mixed).toBeDefined();
• expect(mixed).toBeFalsy();
• expect(mixed).toBeNull();
• expect(mixed).toBeTruthy();
• expect(mixed).toBeUndefined();
• expect(mixed).toEqual(mixed);
• expect(mixed).toMatch(pattern);
• expect(number).toBeCloseTo(number, decimalPlaces);
• expect(number).toBeGreaterThan(number);
• expect(number).toBeLessThan(number);
• expect(number).toBeNaN();
• expect(spy).toHaveBeenCalled();
• expect(spy).toHaveBeenCalledTimes(number);
• expect(spy).toHaveBeenCalledWith(…arguments);

Jasmine functions that can be run before or after tests

To help a test suite DRY up any duplicated setup and teardown code, Jasmine provides the global beforeEach, afterEach, beforeAll, and afterAll functions:

• beforeAll: is called only once before all the specs in describe are run
  • e.g.: to createt the TestBed
• afterAll: is called only once after all the specs in describe are run
  • e.g.: to run some shared teardown after each of the specs in the describe in which it is called.
• beforeEach: is called once before each spec in the describe in which it is called
  • This functionality is very useful for running the common code in the application, lie data initialization.
• afterEach: is called once after each spec in the describe in which it is called
  • Generally used to reset/clean up purposes at the end of specs

Jasmine methods

• TestBed: modulo de angular que nos permite manipular las pruebas y configurarlas.
• SpyOn is a Jasmine feature that allows dynamically intercepting the calls to a function nd change its result.

Testing Cases / How to test...

Testing component creation

• You can see an example at item.component.spec.ts
• this is a very basic test, but it's well documented.

Testing form validation

You can see an example at add-item.component.spec.ts

Testing sharing data from parent to child (using @Input)

You can see an example at item-detail.component.spec.ts

Testing calling a service from a component

You can see an example at users.component.spec.ts

RouterLink

// TODO: pending to code

Testing service against rest api

// TODO: pending to code

• no tengo claro si es un test muy util, porque se mockea la base de datos y da la impresión de que siempre funciona.
• imports: [HttpClientModule]

Testing service against real rest api

// TODO: pending to code

• documentation:
  • https://stackoverflow.com/questions/59204306/trying-to-run-angular-httpclient-jasmine-test-against-live-rest-api-nothing-hap