from Esslingen, Germany...

We are programmers from Esslingen and we are sharing our experience with:

Angular HTTP Testing “SyntaxError: Unexpected token o in JSON at position 1”

tl:dr; Solve this Issue: Add the following line to your imports:

  Full version: A common problem affecting many developers when writing tests for the Angular 4 HTTP service is the following stack trace. It occurs if you assemble an response using a the wrong class. The call of .json()will throw the error.

It throws because the response is of a false type and the body of
Read more…


Can Kattwinkel

Entwickler bei thecodecampus

Avoid Memory Leaks in AngularJS Unit Tests

Memory Leaks When it comes to unit testing in AngularJS there are many things that, developers like us can and will do wrong. The most crucial one is to create memory leaks in our unit tests, which mostly result either in a crash of the unit test runner (browser crash) or in creating a coherence/dependency between different tests that are meant to be separated. This article shows the basic mistakes that are
Read more…

1 Comment

Kai Henzler

Entwickler bei thecodecampus

October 15, 2015

Structured End-To-End Tests With Protractor

The Angular team provides a tool set for creating end to end tests (e2e) called protractor based on WebDriver from Selenium. It’s extended by a deferred element finder and support for the ng-model notation, so it could be the ideal partner for testing AngularJS applications. But if wishes were horses, beggars would ride.

No Comments

Dragan Zuvic

Entwickler bei thecodecampus