Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] plan for ECF 3.4 final days

Hi Wim,

Thanks for looking into this.  I will do as you suggest (temporarily remove these tests...actually I'll leave the code but make them abstract so they won't be run by the auto test infrastructure).


On 10/20/2010 3:54 PM, Wim Jongman wrote:
Particularly see the Twitter test code issue [5]'s going wrong for what looks (to me) like some changes in the twitter service, or the account access or something else.  In any event, please assign the bug to yourself if you


Twitter changed its user/password login and now we need to go through the oAuth protocol. This is all fine and dandy but is looks like quite some work to get to know oAuth and how to let it sing with the REST services. 

I have found a nice library [1] called Scribe that aids in getting request and response tokens in place but this will not be done before 3.4 is released. 

I suggest to get rid of the failing tests for now since they do not prove that the REST services are not working, only that we are addressing twitter in an unsupported way.



ecf-dev mailing list

_______________________________________________ ecf-dev mailing list ecf-dev@xxxxxxxxxxx

Back to the top