GPXReader - initial Endorphine Algorithm

Prerequisites

I've initially looked at my source code and Github and found that I've got few things a bit wrongly implemented (not using properly DRY principle.)

I've found also that gpxreader_test branch should be finally merged to master.

I've found also that android-initial startup as module that as not been …

more ...

GPXReader - Trackpoints Routepoints Waypoints

Trackpoints Routepoints and Waypoints

Before today's change, in my source code for tests I had only trackpoints. This worked pretty well, but then I've figure out, I need to be able to check if someone's going to use different type of *points. And obviously I added this to my steps-to-make …

more ...

GPXReader - Clearing TDD Tests

Introduction

As you might probably read at yesterdays article I've finally found how I shoud follow TDD principle and "flow".

It basically means, I will not create a bunch of tests, but instead I'll create a bunch of not-implemented methods/functions that are documented about their responsibilities but has no …

more ...

FancyBox Plugin and Test Driven Development Flow

Test Driven Development Flow

So lastly I've introduced to myself a Test Driven Development, but unfortunatelly I didn't examine the flow and approach as much as I should.

Thanks to Uncle Bob I've realized what exactly TDD flow looks like.

1. Make a test that (should) fail.

The idea is …

more ...

GPXReader - Business Logic and Tests

Introduction

I've informed you I'll be doing Business Logic for Biking Endorphines.

To make best of my time I've considered to go with TDD and that's why I'll first implement Tests for Business Logic.

This will propably shape all business logic, but I'll have already tests with myself for future …

more ...