Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 2
    What do you value about the tests elsewhere in your system (confidence, fast feedback, ...) and why would you not want that for the Angular UI? Unit and E2E tests aren't either/or, you can use the latter to make sure everything works together while the former checks the finer detail. Angular has built-in testing support, see e.g. angular.io/guide/testing; in general, test behaviour through the public API (for components: DOM, @Input/@Output, interactions with injected collaborators). And unless there's a nuance beyond "worthless", that open opinion doesn't seem at all useful. Commented May 25, 2020 at 14:13
  • 1
    How sure are you that you need unit testing, as opposed to other kinds of testing? Does your angular frontend contain any real logic, does it (re)calculate data, ... or is it more or less a glorified view renderer? What exactly do you want your test to confirm? The general approach is always to define what you want to confirm and then pick the testing strategy that gets you what you want. Commented May 25, 2020 at 15:08