account-console doesn't let to add provided tokens

[Leo Arias]

For authentication with the evernote sandbox we have a developer token that we can use to avoid doing the actual auth dance and authorization.

The account-console tool doesn't let you add the token values to an account.

We are currently duplicating most of account-console code in order to do it: http://bazaar.launchpad.net/~reminders-app-dev/reminders-app/trunk/view/head:/tests/autopilot/reminders/credentials.py#L110

[David Barth (dbarth)]

@Leo: can you make a merge proposal with that code. It looks like an interesting addition to account-console.

[Leo Arias (elopio)]

Not really. Well, I could, but account console is a CLI tool without tests. What we need is a tested library, so if I just move the code to account console it's still not going to be useful for us.
What we need is to turn account-console into a library that can be imported from the python tests, and to make sure that it has tests for all the methods on its API. Or start a new test helper from scratch, test-driven.

[Leo Arias (elopio)]

I think I've mentioned it before, but just to leave evidence here and to be clearer: we need this test helper to have self-tests on its branch so when a new release of one of the accounts components breaks the helpers, the release is blocked. Then the tests for the consumers of the accounts components can rely on this testability library, because it will always work.

[David Barth (dbarth)]

+1 Just merge-propose the current module you have and Alberto will start from here. Thanks!

[David Barth (dbarth)]

@Leo: any progress on the merge proposal?

[Leo Arias (elopio)]

I have some work in progress. But now we are following the scrum process, so I need to wait for my manager to put this on the top of the backlog to continue working on it. This is one of the things we should talk about during our meeting this week. It's not forgotten.