Forum Discussion
4 Replies
Sort By
- omatzuraSuper ContributorHi!
sure.. maybe as input fields on the "Description" tab?
/Ole
eviware.com - alibaba82Super Contributorthat works too. It helps to track down who wrote the scripts when they dont make any sense.
Maybe you can detect if the testcase changed and then then auto populate the field based on user credentials from the system. Not sure if this would be over kill - Hmm should that be a list of "modified by's"
Created By Ali
Modified By Niclas
Modified By Ali
Modified By Niclas
or just the latest modified by.
Created By Ali
Modified By Niclas.
Also should that contain a date? Dates has always helped me when asked why I did a modification. "Oh it was in early april. Don't you remember, in April we integrated with the new payment system"
/niclas - alibaba82Super ContributorI think a data and just a last modified entry should be sufficient. I can see how a list of modified by and reasons are helpful in a development setting but in QA I will usually just rely on the tescase description to understand someone elses description.
Related Content
- 6 months agoClemens
- 9 months agoroopepaajanen