Forum Discussion
hlalumiere
11 years agoRegular Contributor
My usual answer applies here. The ideal way to collect metrics is to insert your results of interest into a database table, then you can query that table to get all kinds of useful information TestComplete cannot give you. For example, whatever verification points are, I assume there is some common routine that is ran on every VP? In that case add an SQL insert query in there to insert the current build, VP ID, date and time, etc, into a table. Now each and every VP is stored in a database. From there you can get:
- Total count of VPs
- Total count of VPs passed
- Total count of VPs failed
- Same counts as above, but build-specific
- Graph of performance, in VP over time
- Etc...
- Total count of VPs
- Total count of VPs passed
- Total count of VPs failed
- Same counts as above, but build-specific
- Graph of performance, in VP over time
- Etc...