Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I just started an open-source project for an Azure table storage client on codeplex called Cyan.
I would like to include unit-tests for the project but I don’t know what’s the best way to store credentials for the tests so that any contributor can use his ones without the risk of checking them in the public source control.
Any advice/best practice for this?
The way I know works great (at least with regular TFS) is to put the unittests into a seperate folder structure and then to customize the permissions on the folder structure (or maybe this is only limited to some specific files) to not let contributors modify those folders. Then you have explicit control over the content of those assets that you need.
What you can also try is to have those credentials stored in files that are not under version control. For a contributor to mess up then involves an explicit add action which can be prevented, by exclusion of that specific file type or by a custom check-in policy, like forbidden-pattern.