| 21:31 | <pzuraq> | 👋 |
| 21:32 | <pzuraq> | So I’ve been working on the decorator tests, and I’m having a bit of difficulty understanding best practices for the desc property |
| 21:33 | <pzuraq> | Specifically, my two main issues are 1. Narrowing down which parts of the spec to include. A single test often involves a number of operations or different parts of the operations, and like, it seems odd to try to cut out each piece |
| 21:35 | <pzuraq> |
|
| 21:35 | <pzuraq> | There were a number of large refactors while I was working on it |
| 21:35 | <pzuraq> | So it seems like drift could become a real problem? |
| 21:36 | <pzuraq> | I get why it makes sense to quote the lines that matter, especially for big blocks |
| 21:37 | <pzuraq> | But also just wondering if, like, it makes more sense to include a high level description and a reference to the section(s) being tested? |
| 22:32 | <ptomato> | pzuraq: you mean the info property, where people usually put direct quotes from the spec? lately, we haven't been placing too much importance on it, for exactly the reasons you mentioned |