Need advice about which tool to choose?Ask the StackShare community!
Emacs vs Jest: What are the differences?
Emacs: The extensible self-documenting text editor. GNU Emacs is an extensible, customizable text editor—and more. At its core is an interpreter for Emacs Lisp, a dialect of the Lisp programming language with extensions to support text editing; Jest: Painless JavaScript Unit Testing. Jest provides you with multiple layers on top of Jasmine.
Emacs can be classified as a tool in the "Text Editor" category, while Jest is grouped under "Javascript Testing Framework".
Some of the features offered by Emacs are:
- Content-sensitive editing modes, including syntax coloring, for a variety of file types including plain text, source code, and HTML.
- Complete built-in documentation, including a tutorial for new users.
- Full Unicode support for nearly all human languages and their scripts.
On the other hand, Jest provides the following key features:
- Familiar Approach: Built on top of the Jasmine test framework, using familiar expect(value).toBe(other) assertions
- Mock by Default: Automatically mocks CommonJS modules returned by require(), making most existing code testable
- Short Feedback Loop: DOM APIs are mocked and tests run in parallel via a small node.js command line utility
"Vast array of extensions" is the top reason why over 57 developers like Emacs, while over 24 developers mention "Open source" as the leading cause for choosing Jest.
Jest is an open source tool with 26.1K GitHub stars and 3.53K GitHub forks. Here's a link to Jest's open source repository on GitHub.
According to the StackShare community, Jest has a broader approval, being mentioned in 263 company stacks & 150 developers stacks; compared to Emacs, which is listed in 96 company stacks and 68 developer stacks.
As we all know testing is an important part of any application. To assist with our testing we are going to use both Cypress and Jest. We feel these tools complement each other and will help us get good coverage of our code. We will use Cypress for our end to end testing as we've found it quite user friendly. Jest will be used for our unit tests because we've seen how many larger companies use it with great success.
Postman will be used to do integration testing with the backend API we create. It offers a clean interface to create many requests, and you can even organize these requests into collections. It helps to test the backend API first to make sure it's working before using it in the front-end. Jest can also be used for testing and is already embedded into React. Not only does it offer unit testing support in javascript, it can also do snapshot testing for the front-end to make sure components are rendering correctly. Enzyme is complementary to Jest and offers more functions such as shallow rendering. UnitTest will be used for Python testing as it is simple, has a lot of functionality and already built in with python. Sentry will be used for keeping track of errors as it is also easily integratable with Heroku because they offer it as an add-on. LogDNA will be used for tracking logs which are not errors and is also a Heroku add-on. Its good to have a separate service to record logs, monitor, track and even fix errors in real-time so our application can run more smoothly.
Pros of Emacs
- Vast array of extensions65
- Have all you can imagine44
- Everything i need in one place40
- Portability39
- Customer config32
- Your config works on any platform16
- Low memory consumption13
- Perfect for monsters11
- All life inside one program10
- Extendable, portable, fast - all at your fingertips8
- Enables extremely rapid keyboard-only navigation6
- Widely-used keybindings (e.g. by bash)5
- Extensible in Lisp5
- Runs everywhere important5
- FOSS Software4
- Powerful multilanguage IDE4
- Git integration4
- May be old but always reliable4
- Asynchronous3
- Powerful UI3
- Huge ecosystem1
Pros of Jest
- Open source36
- Mock by default makes testing much simpler32
- Testing React Native Apps23
- Parallel test running20
- Fast16
- Bundled with JSDOM to enable DOM testing13
- Mock by default screws up your classes, breaking tests8
- Out of the box code coverage7
- Promise support7
- One stop shop for unit testing6
- Great documentation3
- Assert Library Included2
- Built in watch option with interactive filtering menu1
- Preset support1
- Can be used for BDD0
- Karma0
Sign up to add or upvote prosMake informed product decisions
Cons of Emacs
- So good and extensible, that one can get sidetracked4
- Hard to learn for beginners4
- Not default preinstalled in GNU/linux1
Cons of Jest
- Documentation4
- Ambiguous configuration4
- Difficult3
- Many bugs still not fixed months/years after reporting2
- Multiple error messages for same error2
- Difficult to run single test/describe/file2
- Ambiguous2
- Bugged2
- BeforeAll timing out makes all passing tests fail1
- Slow1
- Reporter is too general1
- Unstable1
- Bad docs1
- Still does't support .mjs files natively1
- Can't fail beforeAll to abort tests1
- Interaction with watch mode on terminal0
Sign up to add or upvote consMake informed product decisions
What is Emacs?
What is Jest?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Emacs?
What tools integrate with Jest?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+32