Let me be crystal clear.
I want to make sure we get this straight and certain from the get-go.
When I say testing the Angular router I don’t mean that we’re actually writing tests for the Angular router.
Instead, here’s what I’m trying to say.
A common cause of bloated Angular applications is unneeded imports.
As an application grows, we developers tend to ignore all the dependencies. And we forget to check our imports to make sure we’re not importing things we don’t use.
So how do we avoid this?
How do we make sure…
Why does testing Angular applications have to be so complicated?
Where do you start when you have to write tests for your Angular application?
What are the first steps?
What should you test?
Not sure how to mock a dependency? Or if you should just inject it directly?
Want to skip the read and get to the code right away? Then click here.
Have you ever noticed…
Maybe your experience with Angular has been different than mine but I find that the HttpClient is a…
How do make sure that your Angular application is always production ready every single time it’s deployed?
What can you do to make sure you never deploy a slow Angular application?
How do use the Lighthouse package with your Angular project to make sure it scores well every single time…
angular.json file in the root folder of your Angular project.
Scroll to the
test section and add the
codeCoverage: true line.
Now, when you restart the Angular testing process, you’ll see…
Need to make your Angular app perform faster RIGHT NOW? Then click here to view and download the complete Angular performance checklist.
Otherwise, if you want to dive deep…
…into all the mechanics and logic of how we improve the performance of an Angular application, then read on.
Some Angular developers grumble about the jumbled output that appears in the terminal when they test their Angular applications.
They want a nicer report that’s easier to understand at a glance….
Karma Mocha Reporter to the rescue!
Once installed and configured, here’s what the outputs will look like.
How do you do it?
How do you add a login form to your Angular application?
And how do you make sure that users that aren’t logged in automatically see your login page? And the logged-in (authenticated) users see the dashboard or something else?
Data models are the backbone of any .NET Core API server.
At least, that’s been my experience.
And building on the data models are the API controllers that give the world access to your data.