I have a few questions about conventions observed in writing IGT tests. I don't see any standard wrapper for logging other than the logging that goes with certain igt_ control flow functions. Is it recommended to limit logging to just these? I see some different approaches to supporting verbose modes. Is it just up to each test? Any recommendations on subtest granularity? Testing boils down to repeated cycles of 'do something' then 'assert something'. Just wondering if there is a guideline on how many of those cycles should each subtest contain. Probably this is very case specific. Also wondering if something like an igt_warn function to go with igt_require and igt_assert has been considered. There might be a case where some condition is not met which causes the test to become limited in its effectiveness but still valid. We might still want to run the test and let it pass but attach a caveat. Or would adding this gray area just be too complicating. Thanks Jeff _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
