[Webtest] Traceability Canoo Webtest Newbie

[Marc Guillemot]

Hi John,

where would your "profileId", "ccidId" or "processId" come from? Is it something 
you would like to add to a webtest in a way like

<TestSpec name="My great webtest">
	<dummyinfos>
		<profileId>123</profileId>
		<processId>54665478</processId>
		...
	</dummyinfos>
	&config;
<Steps>
...

And should just be written in the report "as it"?

Marc.





Smith, John C wrote:
> To:  webtest community
>  
> Can anyone offer any kind of direction of implementing a simple solution 
> to include traceability within my acceptance tests?
>  
> I would the ability to look at a summary report that will allow me 
> to drive test cases (traceability) back to the requirements/profile
> 
>     * Below are items I would deem vital for producing metrics
>       associated with our testing efforts:
>     * I believe we could add these nodes to the xml test template and
>       they could be extracted via XLST to produce HTML reports.  
> 
>                  profileId - This id represents our internal project 
> numbers associated with our wave development.
>                  ccidId -  This id represents our requirements document.
>                  processId - (Accruals, Billing, Buydown & Subvention, 
> etc....)  - This id represents our internal functional processes.
>  
> I am envisioning a report that can be viewed at any of the levels 
> mentioned above.  Here a quick and dirty sample
>  
> Accruals
>     1  Add new accrual group
>     2  Delete new accrual group
>  
> Billing
>  
>     1 Add new billing customer
>     2 Delete new billing customer
>  
> If anyone could be assistance it would be greatly appreciated.
>  
> Thanks,
>  
> John <mailto:john.c.smith@fnf.com>
>  
>