Some of you probably noticed but we are working to improve the first experience with OctoPerf.
At first with video tutorials which show all the features:
This is a must-have to quickly rework any existing virtual user. Any action can now be disabled to prevent it from being executed when running the virtual user. Actions no longer need to be removed from the virtual user to be taken out of the execution. This feature is especially useful to debug virtual users by running repeated validations.
Immutable objects have multiple advantages over mutable objects which makes them the perfect building block to create software. You may already have many questions about the subject like:
Why should I use immutable over mutable objects?
How can I design software where no single object can be modified?
You'll see in this article what an immutable object is, the advantages to use them every time you can and how they can speed up your software developments.
To make it simple, a class is immutable when instances of this class cannot be changed once constructed. Immutable objects follow five rules, like explained in Java Effective by Joshua Bloch:
It involves mocking the Angular2 Http service, and it's far more complicated than unit testing the Router service.
I first tried to inject a mock of the Http service and return custom Observable responses but this led to strange errors and cumbersome code.
I quickly switched to the recommended way, using MockBackend.