In Web Accessibility Hacker Way I mentioned that “only 20% of accessibility requirements can be verified by tools”. Nevertheless, it is worth to cover this 20%. Especially, when it is not very hard. You know that having automated test that guard against regressions always pays off in a long run.
Web 3206 dni, 18 godzin, 8 minut temu 50 pokaż kod licznika zwiń
Podobne artykuły:
- [EN] NSubstitute and the search for perfect error messages
- How to test a class that has constructor impossible to mock? | Dariusz Woźniak | Blog
- Maciej Aniserowicz | [UT-3] Mocki
- [EN] TDD with TypeScript, AngularJS, and Node.js
- Maciej Aniserowicz | [UT-4] Co testować, a czego nie testować?
- Node - Mockowanie request-ów w testach jednostkowych - bd90
- [EN] Unit Test code with static method Console.Write | Passionate Programmer
- Piszmy unit testy! | maciejjędrzejewski
- Rhino Mocks vs moq vs NSubstitute | maciejjędrzejewski
- Programming warfare – .NET klasy internal a testy jednostkowe
- TDD master classes by Roy Osherove - Tymoteusz Kęstowicz