Boostnote functionality grows incredibly fast. Core components became huge and bloated with logic. We should start components refactoring, but, frankly, I'm scared to do that without at least basic set of tests. Unfortunately, we don't have any.
I propose to use usual testing stack Enzyme+Mocha+Chai to test components. Then we can step by step add tests for components before refactoring. I can start this process in my #1557
@kazup01 @Rokt33r What do you think?
nlopin
All 6 comments
I prefer jest. How do you think Jest?
Rokt33r
on 21 Mar 2018
I prefer jest as well, easy to configure, mock and most impotantly snapshots 馃憤
rayou
on 21 Mar 2018
Let's try Jest, it's just a matter of choice. I can add it to the project today
nlopin
on 21 Mar 2018
@nlopin I appreciate your contributions. I'll gladly wait for it. 馃挴 馃挴 馃挴
Rokt33r
on 21 Mar 2018
@nlopin @Rokt33r What is the current status on this? Are there any points that still need to be discussed about this?
Flexo013
on 1 Aug 2019
I'll close this since we are actively using Jest.
For continued discussion on Jest and test coverage let's use #1826
Flexo013
on 7 Aug 2019
Related issues
shunchuan
路
3Comments
luong-komorebi
路
3Comments
Ocanamat
路
3Comments
aurelkurtula
路
3Comments
gavvvr
路
3Comments
Most helpful comment
Let's try Jest, it's just a matter of choice. I can add it to the project today