You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
funcTest_getKeyLength(t *testing.T) { ... } // package-level function
145
+
```
146
+
147
+
### Test Ordering Conventions
148
+
149
+
Constructor functions (`NewXYZ`) should always be declared first, at the top of the test file. After constructors, test functions should be ordered alphabetically within each file. When a file has logical sections (separated by comments), tests should be alphabetical within each section. Getter and setter functions are grouped together under the base name — ignore the `Get` or `Set` prefix when determining order (e.g. `Test_AppName` and `Test_SetAppName` both sort under `A`). Exceptions to alphabetical ordering can be made when it doesn't work well for readability or logical grouping.
150
+
138
151
### Table-Driven Test Conventions
139
152
140
153
**Preferred: Map pattern** - uses `tc` for test case variable:
0 commit comments