But, what about Data Smells?
In this post we discuss top smells that indicate you need Test Data Management.
In computer programming, a code smell is any characteristic in the source code of a program that possibly indicates a deeper problem. Determining what is and is not a code smell is subjective, and varies by language, developer, and development methodology.
Invariably every IT problem has a symptom that we call smells.
In this post lets focus on the most popular ones associated with Test Data Management
Top 15 TDM Smells
- Testers waste large amount of time creating data rather than testing the application.
- Data provides doesn’t meet the requirements for testing (has incorrect mix of data).
- DevTest cycle /and project slippage to data unreadiness.
- Dependency on other experts to provide the Test Data (experts that may have other priorities).
- System Data lacks integrity (is incomplete) and limits System Testing.
- Up or Down stream data hasn’t been prepared in similar fashion, causing E2E integrity issues.
- Data Related defects caused by data being in unrealistic state i.e. False Positives.
- Test Data Creation is (or is deemed) too complicated or time consuming.
- Test Data is too large causing refreshes to take too long.
- Test Data size (production size) causes performance bottlenecks & broken batch processing in smaller test environments.
- Data has been copied from production and has PII data i.e. Data is insecure.
- Testers (& developers) don’t understand what the platform data looks like. Resulting in the engineers fumbling in the dark as they try to exercise it effectively.
- Due to Data complexity, Testers can’t easily find (mine) the data sets once it has been deployed.
- Test results are being corrupted by testers “only” using/reusing the same small data sets (data contention).
- Lack of data reuse (or automation) resulting in continuous reinvention and repeated mistakes.
Test Data is an essential, if not somewhat complicated, and often ignored, aspect of effective Devops & Quality engineering. However treating it as an after thought will invariably result in the smells described above. Smells that will introduce suboptimal DevOps/DataOps operations, unwanted project delays and poor testing.
Do you have other ideas on Test Data Management Smells, then please let us know?
Post By Jane Temov
Jane is an experienced IT Environments Management & Resilience Evangelist. Areas of specialism include IT & Test Environment Management, Disaster Recovery, Release Management, Service Resilience, Configuration Management, DevOps &Infra/Cloud Migration.