Skip to content
This repository has been archived by the owner on Oct 2, 2018. It is now read-only.

Implement automated testing #265

Open
ferndot opened this issue Dec 18, 2014 · 4 comments
Open

Implement automated testing #265

ferndot opened this issue Dec 18, 2014 · 4 comments

Comments

@ferndot
Copy link
Member

ferndot commented Dec 18, 2014

It would be good to have automated testing so that we don't break things unintentionally.

First, what service should we use?

@twiss
Copy link
Collaborator

twiss commented Dec 19, 2014

Wish list:

  • Run the test suite everywhere Firetext runs
  • Both automatically and manually (maybe even included in the Firetext app?)
  • Emulate actions in designMode, such as pressing enter (http://stackoverflow.com/a/10520017?)
  • Reftests (okay, maybe now I'm asking too much.)

@Ryuno-Ki
Copy link

I learned Jasmine first, but had problems when it comes to persistent storage (NodeJS file API).

Mozilla use ChaiJS together with Mocha.

So I'd say it comes down to what you want to test.

@ferndot
Copy link
Member Author

ferndot commented Dec 19, 2014

I have seen Travis CI used for running tests.

I am not too familiar with testing, but I would think that we want to test any interaction that the user can make with the app. Also, we want to extensively test the parsers.

@Ryuno-Ki
Copy link

Travis is Continuos Integration service, that is, it runs the test for you every time you push to GitHub (if configured to do so).

Parsers could be tested through unit tests with the tools I mentioned.
The other thing is called end-to-end (or integration) testing. I have some experience in unit testing.

What I like is code coverage, since they report about how much is tested. You know the pareto law ;-)

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

3 participants