Dojo

Proposal

To improve our mindset of writing well tested code, following Test Driven Development, we believe that hands on experience is the quickest way of learning how to write tests that will help guarantee quality for our apps.
It started focusing on frontend code based on AngularJS because it became a great gap lacking unit testing the UIs in most of our teams. We are also developing server APIs to support client actions, making the app usefull. Octávio chose to develop the API in Go because he wants to boot up his necessity on learning the language, focusing on TDD principles, of course 😇

What's being developed

We've started an app from the ground up. It's meant to be an external layer on top of our disgusting time tracking app, delivering some extra features like:

• Improved UI, responsive and more pleasant for mobile
• Quicker access with better authentication
• Keep own data base to let user adjust (possible forgotten) tracks
• Report all time tracking any Month, anytime

This app is designed to serve as a good example of well tested, clean & always working project.
Later, we plan to take some "bad examples" and code tests for them, helping it evolve with better quality.

Further Info

This repo is currently a work in progress regarding it's scope. Feel free to send us your suggestions, complains, difficulties and most importantly, communicate how you are promoting quality in your projects 👍

Contributing Tips

Want to dive in & get your hands on coding? The project is organized into two main folders: api & client.

Frontend development

Our client app src together with it's package configuration are all stored at client.
Having npm installed in your host, there goes some basic steps to get you running it:

cd client
npm install
npm test
#or
npm run watch:test

Backend development

A Go backend implementation resides in api.
To start a working server or run existing tests:

cd api
go run main.go
## Test it
cd model
go test

Some disclaimer about our time-tracking app

We are still discussing which code standards to follow, what tools to use, how write our test cases and so on... Be part of it contributing with your ideas!

Meetings happening most fridays at 4 pm. Join us 👐