There is nothing more frustrating than trying to run a testing API and getting a super cryptic error, or having your breakpoints ignored. In particular, I’m talking about running Jest tests with an IDE and using its debugging facilities when talking to a training class. However, some of my latest frustrations (self-inflicted, of course) center around running Jest tests for React projects. Whether it’s the test runner, the proper testing API, picking the appropriate mock/spy/stubbing strategy, dealing with async code, it’s always a tad complicated. Those of us who have worked with JavaScript testing APIs on various platforms shudder every time we think about configuration issues.
0 Comments
Leave a Reply. |