guidelines for testset descriptions and structure #19625
Open
Description
opened on Dec 16, 2016
Guidelines for testset descriptions and structure would be useful. Some points potentially worth documenting:
Should testset descriptions fully describe the associated tests, or just provide a title and leave full description to an adjacent comment? If the former, should testset descriptions be complete sentences? If the latter, title case and comment placement conventions?
How fine grained should testsets be? Should they contain some minimal number of tests, or should an isolated test (e.g. a single-line issue spot test) have its own testset? Within a testset, should different subsets of tests be enclosed in their own testsets, or should they be demarcated by comments? Best!
Activity