This is a typical "stateful test data management" issue: keeping track of test data records that are flagged as some kind of "used". You could use Silk Performers simple file functions to handle this, but I consider this as a very limited workaround only. There is no "CsvFileUpdateColumn" function in Performer - at least not up to v 18.0. The better option is to establish a central test data management using an external database, e.g. mysql. You can then use Silk Performers database functions for "CRUD access" to your test data: create, read, update, delete. Another advantage: You can automatically gain test data consistency for all your load test agents when all of them share a database that contains your test data. When using regular CSV files (being distributed over a couple agents), all you have is FileGetNextUniqueRow() - but with this you can't flag this row persistently as "used" or add any custom information. And if you ever need to do a "test data reset" just re-import an initial DB dump.
↧