| || |
I have huge test data to test , with multiple options and combinations ,what is the best way to test such huge data ,and how to keep track of the what data has been tested , is there any thing i can do manually without using any tool
this situation i have faced in many project ,what happens is i tend to randomly test some data and cannot track what has been tested and what not. resulting in missing on some combination , which later results in defect in UAT or production
can anyone sugget how to manage Test data
On reducing what you need to test, look into the topic of K-maps and orthogonal pairs testing. K-maps will group the items into what matters, and orthogonal pairs will reduce the testing to cover single and double points of failures (but does not cover triple and above), about 80% of all bugs you see are double points of failures, and 15% being single point of failures.
As to how to manage test data. That's a very long and complicated subject, there's tons of debate over best practices like, test data set database scripts vs Fixtures vs Factories, Object Mother vs Data Builder patterns, etc...