HN user

vesln

304 karma
Posts33
Comments5
View on HN
github.com 10y ago

Show HN: Assertions and utils for testing React Components

vesln
5pts1
belonganywhere.com 11y ago

A true story about belonging by Airbnb

vesln
1pts0
www.apple.com 11y ago

iOS 8 – Now available

vesln
1pts0
vesln.github.io 12y ago

Captureme – CLI utility that captures screenshots via browsers in the cloud

vesln
1pts0
klinger.io 12y ago

Easy, but easy to f*ck up. 3 Rules to Setup Analytics Tools correctly

vesln
10pts1
www.vimninjas.com 12y ago

Testing Vim Plugins With Vimrunner and RSpec

vesln
3pts1
github.com 12y ago

Hippie - a Node.js tool that enables you to write blazing fast API tests

vesln
1pts0
github.com 12y ago

Nixt — Simple and elegant end-to-end testing for command-line apps with Node.js

vesln
2pts0
github.com 13y ago

Elegant Range implementation for Node.js & the browsers

vesln
2pts0
github.com 13y ago

Obsessed - Retry mechanism for Node.js and the browsers

vesln
2pts0
github.com 13y ago

Build blazing fast RESTful API clients with Node.js

vesln
1pts0
www.vimninjas.com 13y ago

HappyEdit - an HTML5 Remake of Vim

vesln
1pts1
news.ycombinator.com 13y ago

Ask HN: Where to promote posts about code

vesln
2pts0
github.com 13y ago

Easy testing for time-dependent code - Node.js

vesln
1pts0
github.com 13y ago

Robber.py - BDD / TDD assertion library for Python

vesln
1pts0
www.vimninjas.com 13y ago

Light vim color schemes that you should consider using

vesln
4pts1
www.vimninjas.com 13y ago

Code Substitution Done Right - Switch.vim

vesln
37pts12
www.vimninjas.com 13y ago

Plugins you should put in your vimrc

vesln
164pts95
www.vimninjas.com 13y ago

Vim for Rubyists

vesln
2pts0
www.vimninjas.com 13y ago

10 vim color schemes you need to have

vesln
10pts13
github.com 14y ago

Is my site up? Node.js edition

vesln
1pts0
github.com 14y ago

Teacher - Spell checking for Node.js

vesln
1pts0
github.com 14y ago

Jack - a simple but yet powerful mock framework for Node.js

vesln
4pts0
github.com 14y ago

A caffeine driven, simplistic approach to benchmarking Node.js code.

vesln
7pts3
github.com 14y ago

Surround.rb - surround a method with before and after functionality.

vesln
1pts0
github.com 14y ago

Reddit and Hacker News in the CLI.

vesln
2pts0
github.com 14y ago

Todos in the CLI like what.

vesln
31pts23
github.com 14y ago

I've just made a chat bot.

vesln
3pts0
github.com 14y ago

Simple process monitoring with node.

vesln
2pts1
github.com 14y ago

CLI tool for GitHub Issues

vesln
52pts17

Hello, Hacker News!

Author here. I'm super glad to share something that we have been working on during the past couple of days. A bridge that connects the chai.js assertion library and enzyme - airbnb's library for testing React components in isolation and in integration.

A little bit of background - we developed a project that was very similar to enzyme, focusing on encapsulating the differences between React's shallow rendering and mounting into the DOM (jsdom). However, once enzyme came out, we decided to stop investing in it and instead migrate to enzyme.

I'm personally a bit surprised that people don't define many custom assertions in their projects, while IMO they should. There are a number of great benefits such as better exception messages better diffs, DRY etc. I'm also a chai.js maintainer, and I would love to know if you have custom assertions in your project. If so - what can we improve there, and if not - how we can make it easier for you to start utilizing this ability.

The assertions is just the first piece that we are open sourcing. We have an internal lib for creating factories (ala factory girl) coming out next and more that we'll be trying to get out in the next couple of months.

So please hare your experience with testing your frontend. What are you using? What are the biggest issues you are facing? What do you want to see improved?