Skip to content
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.

web/client Unit Tests/E2E Tests #45

Open
gumbyscout opened this issue Mar 29, 2016 · 3 comments
Open

web/client Unit Tests/E2E Tests #45

gumbyscout opened this issue Mar 29, 2016 · 3 comments

Comments

@gumbyscout
Copy link
Collaborator

We seriously need to start writing at least unit tests for the web client. Writing 'good' tests never has really clicked with me, so I'll definitely need help from someone else when it comes to giving the web app code coverage. Also, we need to determine what test runners/frameworks we want to use so I can some how integrate them into our build, possible through creating a gulp script or the like. Thoughts?

@nictuku
Copy link
Owner

nictuku commented Mar 29, 2016

I spent a few minutes reading about gulp and I did not fall in love with it. It seems way too simple to be useful for me. It's just a shell script /Makefile in javascript ? :-P

I'm a bit that surprised gulp seems to be the industry standard.

I guess we also need to find the web test framework itself. I only know WebDriver and friends.

@gumbyscout
Copy link
Collaborator Author

Gulp is more than a makefile. It's a streaming task runner that has access to web technologies that we are using as first class citizens. If it runs on node, you can plug it into gulp, and a lot of tools even have specialized interfaces for gulp to use. If JSPM wasn't handling our module loading and minification, you could write tasks to concat, minify, transpile, and export all the javascript files, while also running tests on them and making sure they fit our coding guidelines. You can do complicated chains pretty easily.

@gumbyscout
Copy link
Collaborator Author

I got a test runner working yesterday, and with react's testutils, you can effectively do E2E tests with it. I.E. you can trigger events and such.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants