ProjectEvergreen / project-evergreen

Wiki and high level "feature" tracker for Project Evergreen
https://projectevergreen.github.io/
Apache License 2.0
11 stars 1 forks source link

As a developer I would like to have Karma evaluated for unit testing #44

Closed thescientist13 closed 5 years ago

thescientist13 commented 6 years ago

Type of Change

Summary

In chatting with community members in Polymer Slack, I had a productive discussion about the merits of using WCT, Jest and Karma. A few of my thoughts coming out of that chat:

Jest

WCT

Karma

Use Case

TBD - need to do some discovery first

Code Sample

TBD - need to do some discovery first

Pros / Cons

I think evaluating alternate options for testing is a good idea, especially if that option can provide a more ergonomic developer experience. I guess the question should be after this exercise is complete, is there a place for two solutions, or just one?

If Karma can provide a compelling / better experience, I say it might make sense to stick with one solution, just for support / documentation sake. Links to other docs would be good too.

thescientist13 commented 6 years ago

Links

thescientist13 commented 5 years ago

Got an implementation working in CEA https://github.com/ProjectEvergreen/create-evergreen-app/pull/14/

thescientist13 commented 5 years ago

Implemented with Karma in CEA. Open to anyone who wants to add this to the Todo App or the website.

Wiki updated here https://github.com/ProjectEvergreen/project-evergreen/wiki/Unit-Testing