In my company, we use a separate test environment where we copy production data daily. This environment is periodically used to detect issues like the ones you have encountered.
The vast majority of our testing is carried out with synthesized, non-production data. Some of this is produced by hand, but most is produced by scripts we build. We periodically ...
Depends on your definition of testing, anonymized data is widely used by Microsoft and others for monitoring and testing in production, it's the basis for A/B testing or monitoring for example.
In Europe the GDPR does not allow usage of private data, but the GDPR does not apply to anonymised information and anonymised data can be used without consent. ...
Verify name is mandatory or not
Enter the value as blank spaces on mandatory fields and click on Save button
Enter the value as Special Character & Numbers on mandatory field and click on Save button (a. 12345, b. /--+-,
Check Data type(s) for required field
Enter value as "a to Z" and check the character length and click on ...
I wouldn't say it is common to use real data in testing, although the customer might provide a subset of "real" data in order to facilitate the process.
Apart from the privacy and business issues, there are also the legal ones, e.g. General Data Protection Regulation (GDPR) has been enforced since 25 May 2018 in Europe (but I think every company dealing ...
Is there a general best practice for this? We already scrub sensitive
information when using data in our test environments, but what about
scrubbing less sensitive information such as email address or phone
Most shops have practices for using test data. The specifics differ, but in general you don't want to use Production data which would be ...
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 for a large number of lookups. That means that any method of anonymization must ensure that the social security number of a given person must produce the same ...
Ideally I would like to write the test based on a file that approximates what my script would be actually processing, rather a much much smaller sample size.
If it were me, I would test functional correctness and scale independently. Fault isolation is easier that way. Your code/test/debug cycle can go more quickly too.
The thinking here is that ...
I haven't heard of a standardized term for this technique, but it is commonly used. We do this pretty regularly at my current company, but avoided it almost completely when I worked at Microsoft, even though there were a number of cases where it could have greatly improved our ability to troubleshoot issues. At Microsoft, they considered the risk of ...
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 standards.
That said, the scrubbing method doesn't have to be terribly difficult - if there has to be something in those fields, set all the email addresses to a ...
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 except...)
Some examples you can use:
Copy/Paste the entire text of Hamlet (thanks to QA Hates You for this one (you'll have to google for it - I don't have ...
As UI tests are slowish I think its important to be able to run them in parallel. In order to be able to run them in parallel your data-management becomes even more complex, since if the tests use the same data-source they could change data into conflicting states and make tests randomly fail, that why the tests should all run in isolation.
Currently I am ...
You need to verify following things:
Verify the downloaded report is in correct format for example if you select pdf option then pdf should get downloaded and not html or other
Verify the name of downloaded file is as expected, many a times file has some naming conventions which are followed
Verify the header and footers if any
Verify the calculations ...
All options are displayed
All options are enabled
Multiple selection is not allowed.
If multiple selection is allowed, check if you are able to achieve it.
If radio button is a necessary field, check if not selecting it raises an error message
If any event is associated with radio button, check if that's happening correctly.
Click on radio ...
IVR (Interactive Voice Response) applications allows
customers to call and navigate through various instructions
to Login, check on account, pay bills, order service, Customer call, Raise complaints etc.
IVR applications interacts with the caller to determine (via collection
of customer entered dtmf digits) who is calling and the reason
for the call.
Some tools for test data generation - online and standalone:
Datagenerator - free tool, DB data / tables generation.
GenerateData.com - free online script-based data gen, different output formats, including CSV, Excel and SQL.
Spawner Data Generator - sample/test data for databases.
More links may be found here, but the above 3 I use more often and they're ...
The first two issues that come to mind are scalability and tolerance of faulty data.
Data Science frequently implies large data sets. As a tester, you need a sense for expectations about data set sizes and the corresponding performance. Those metrics need to be put in the context of the computing environment of course; what you can do on a laptop running ...
Welcome to SQA, Rumi P. It sounds like you have a bootstrap problem rather than a chicken-and-egg problem. There is nothing intrinsically wrong with using software under test to create your test data, especially if it lets you write and maintain tests more easily.
Of course if you don't implicitly trust your Linq classes, you should test them. One way ...
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 lowest risk (expressed as a relative number, e.g. 1 being the highest risk and 25 the lowest) and state a few of the biggest risk factors for each potential solution....
You need to mock the request to the API.
Here is a PHP example: https://github.com/InterNations/http-mock/blob/master/doc/start.md
What this example does, is start a small fake http server, which always returns that data that you expect/need for the test.
You can also start a seperate mock-server manually and use that to test against. Read more at http://...
When someone asks me a question and I don't know the answer, I tell them I don't know the answer, and then I ask them to tell me what they think the answer is. Maybe you should do that next time. If you're an interview, I don't think you'll be judged worse for asking, since either way the interviewer already knows that you don't have the answer. And it's ...
Personally, as the "service test" is the end-to-end test and the expensive one, I'd just put in some simple values that I know are good. As this is a single test with fixed parameters, I'd just pick some numbers. I'd likely pick different numbers than in lower level tests if they had fixed values, just for the slight increase in coverage. (Though ...
Principles related to the processing of personal data
Personal data shall be obtained only for one or more specified and
lawful purposes, and shall not be further processed in any manner
incompatible with that purpose or those purposes.
So as per data protection law applied, production data can’t be processed for ulterior purposes from when it was ...
Data security and privacy standards vary from country to country around what can and cannot be stored, and are generally only guidelines not legislation.
That said, if your management are saying that data needs to be scrubbed, then it needs to be scrubbed regardless what the technical team thinks.
There are other ways to look after data that do not require ...
Best Practice I always find as a loaded term. While there are industry-wide practices some of those may be lenient in any particular space or be far more strict, especially in places where there is a lot of Personally Identifiable Information (PII) or financial information. Much of that PII has to be very well protected, or you can encounter situations ...
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 the data store - the simplest method you can use is to perform an operation with your application and treat the data store as an oracle for verification ...
I found this site that offers a sample of user agents in csv format:
Actual download link:
The format is: