Search Results

I'd suggest taking a look at this question and the answers first. There's some good information in this question as well. The amount of data cleaning you need to do will depend on your application an …

You should absolutely be scrubbing email addresses and phone numbers. They are, as others have said, personally identifiable information, and failure to scrub them is a breach of data security standar …

There are a few variables here: Will the tests modify the data? - If they will, you'll need to reload the data as a precondition for each test. How long does it take to load the data? - If it takes …

The method used at my current location is a slight variation on the suggestions above: Each team member has a personal superuser login whose password is known only to them. Each team member then res …

Honestly, the only limit is your imagination. You'll find out pretty quickly if the programmers took the permissive approach (allow everything except...) or the repressive approach (prevent everything …

Welcome to SQA. As @user246 says, there's nothing intrinsically wrong with using your application under test to generate your test data - although you probably do want to have tests that validate the …

Based on your response to my comment, you're not actually looking to test database operations but an application that employs the operations. That makes things a little simpler. If you have access to …

Here's how I'd approach this situation (the tl;dr version): Analyze your options and give an indication of the risks involved. Your risk analysis should show your preferred option as having the lowes …

As I understand your question, the answer is to use different instances of your object, since they will have a number of common attributes but the attributes your two tests are checking are mutually e …

Would you use the same test data as used in the service test, because you have the expected results already available, or would you deliberately choose different test data in order to implicitly te …

It depends In some industries it's not feasible to test without customer data. Sometimes it's not possible to properly anonymize said data - I test software that uses the US social security number fo …

You're definitely on the right track here. I would start by collecting actual requests and responses generated by the live system, then anonymize as needed. These would be the seeds of your tests, sin …

The Big List of Naughty Strings is another good one - it's not just diacritics, but a whole lot of different unicode strings and a bunch of other strings that are known to cause problems in different …