- May 23, 2014
Really liking what I see in Cypress.ioTwo things that we're doing in my project that help are: automatic test coverage, and plugging in a bug reporting tool.
For the front-end e2e tests (end to end), we're using cypress.io. Cypress has a lot to love about it form a developer's perspective... using it seems to actually make recruiting easier. Capybara is another good test automation option, like @csalvato mentioned. Lots of stuff exists out there that is already written... you just need to add your tests, and any time you push new code you have confidence that the things you're testing for aren't going to go wrong again.
For bug reporting and info collection, one thing we're using is sentry.io. Basically if something goes wrong, usually an unexpected situation in the app (we tested assuming you have customers, but you deleted all customers and went to page x), instead of just failing silently in weird ways you get a nice pop-up that says "whoah, sorry we messed up. Can you tell us what you were doing here?" As soon as we put this in a beta user sent us a report... we would not have even known there was a bug without it because the situation escaped our automated and manual testing. Got a bug report, developer was able to respond by email within an hour letting them know we're on it and pushing a hot fix. Ta da.
I agree with this, although I see people get by with
redneck engineeringbootstrap coding for their MVP and I don't see any problem with that. I've totally done it. But as your project matures and money comes in, it's definitely worth allocating some of that toward automating the tests, improving the code base, putting in bug reporting and other tools to help with users, etc. At least, that's my opinion, but I think it helps scale the business and keep the owner and other team members from getting stuck as career bug-squashers. Currently I'm working on a project where we start with a more mature "done rite" code base, but that's possible because we took the time to do the previous project right (after doing it "good enough" and then reinvesting).
I binge code and it doesn’t always look the best but it works and I’m strict about versioning. Great to see what other polished people are doing.
Don't like ads? Remove them while supporting the forum. Subscribe.