I've looked on the Yodlee website but I can't see any documentation on how best to do test and development.
We have been allocated a private sandbox for testing but the API does not allow adding users. There doesn't seem a way to add them either so it seems pretty pointless.
I registered on the developer portal and got our code working with the test users generated there but this expired after 30 days so is not a viable option for continued testing.
Is there a way to add users to the private sandbox?
If you have been allocated a private sandbox for testing they you can use register3 API to add test users and then continue with your testing.
Related
I want to test transaction on coinbase, is there anyway to test transactions on coinbase development without using real bitcoin. Because I don't have any bitcoins in my account.
As i was also looking for a sandbox environment, i just came up to one of there support, they are no longer supporting sandbox environment for a long time now.
Check out this Answer on coinbase support
There is no way to use any kind of testnet but you could always have a friend create an account and then use the API to send to each other via Email address for no fees.
i need for my application to create and generate test linked in accounts for every time i run my tests. I have researched and found only this solution which won`t work for me : https://developer.linkedin.com/legal/api-terms-of-use 2.3 Test Account
You may create up to five LinkedIn test accounts for purposes of testing your Application only. You must create the accounts manually and not via any automated means, such as scripts.
These test accounts must not interact with non-test accounts (for example, you can’t use test accounts to comment to posts on a Company Page and you can’t connect test accounts with non-test accounts, including your LinkedIn account), or override our API call limits. You must clearly identify the accounts as test accounts in the applicable account profile, and must identify these additional account profiles as “Developers” in your Application registration. You may not create any profile positions at real companies (besides your own) through the test accounts.
I will need more than 5 test accounts and also would like to skip the registration of my application into linked in with Real Data...
For facebook integration i managed to make this using https://developers.facebook.com
If someone have any suggestions or solutions please help :)
As per the terms of use you stated in your request, what you are asking for is not available via LinkedIn at the moment. You will need to change your testing strategy.
I can see many related questions on SO, but none that answers exactly what I'm confused with.
I'm using Google Calendar API in a .NET desktop application that allows user to provide his/her username/password, logs in on his behalf and adds some events to the calendar. Now I want to do exactly the same thing for Tasks feature. I'm trying to use Google Tasks API for this, but have been told that I need to do some OAuth kind of authentication, and even before that, I need to go to my gmail account and set permissions and get my project "key" to enable it.
Now does every user of my application need to do these steps in their Gmail account? Or do I need to do this in MY gmail account once and then my application code will be able to use the generated project "key" to enable my users to add tasks to THEIR gmail tasks list?
Figured it out. For anyone having a hard time understanding this, here it is:
The "key" generation step needs to be done only once per application, not for each user who's going to use your application. To generate a key, login to your Google Account and go to Google APIs Console page. Click API Access button and that's where you can generate keys for different kinds of applications like browser apps, desktop apps, Android apps etc. After registration, you'll need to take Client ID, Client secret and API key from this page and put them into the code. Sample code (.NET) for task creation and several other Google features is available here.
Once your user runs your application, he'll be taken to his Google account in his default browser where he'll be asked if he wants to allow this application to write to his calendar/tasks list. This page will display your logo and description text too that you can provide at registration time. Once allowed, this step won't be required again in the next one hour (this may be adjustable, i don't know yet).
I am pretty sure I missed something, but I couldn't find (ie. google) a possibility to create test accounts for Google Plus.
However, it is surely not allowed to create fake user account for tests, so, how do I test my G+ apps with more than one (my) account?
As you point out, your Google+ account should be created using your common name, but you are not limited to one profile. For manual testing you can create a second profile.
If you are doing automated testing, though, this is probably not an effective approach. Your tests will consume your quota so whenever possible mock the client library to test your code.
Facebook allows you to create test user accounts that can only be used for testing purpose.
Does Twitter provide similar functionality ? I don't want to get my application blacklisted for creating fake user accounts; do I have to use my real user account for testing my application ? What strategies are your using for testing application with Twitter ?
As far as I know, there is nothing in Twitter's rules against creating account (unlike Facebook, where with the exception of test accounts, you're not allowed to create multiple accounts for testing purposes). So, you can just register the account like you normally would.
You might want to take a look at this post for some other tips for test accounts (hiding your tweets, deleting the account when you're done testing, etc.).
I'm currently creating a Twitter application and here are some of the strategies I'm using.
I create my accounts in combination with Gmail addresses. If I create a gmail account as user bob#gmail.com , I secure the Twitter name #bob on Twitter. That way it's kind of hard to forget where to email a lost password. I don't go crazy, as I don't need 100's of test accounts but I do have up to three.
I log on to my test accounts using Chrome because it will automatically recall your password as soon as you type in your Twitter name on the home page. That way it is easy to switch between them, but note that I find it hard sometimes to know which account is actually active because I'm constantly looking at other profiles. This gets confusing if I don't constantly look at the logged in user icon indicator.
Never, ever re-tweet anything unless you absolutely have to for a test case or use hash-tags unless for a test case. Unbelievably even on a completely un-publicized account, I had a few surprise Twitter users in my DB a few seconds after I re-tweeted a link.
on Localhost, close all your other browser windows while your testing. Especially if your calling the API through AJAX. You never know which sites you have open whom also call the Twitter API through AJAX, and this can seriously screw with your tests and rate limits. Especially when your developing live.
I would not recommend protecting your tweets. It's too limiting for most use cases.
For my site, I need to place a link in the tweets. Twitter will not
allow live links to http://localhost so you have to plan around
this and have a live test server sooner then you may anticipate.
Twitter has one of the easiest registration processes I have seen. You can quite easily create several test accounts; this is the only method I have used.
Here is a blog post about it.