Timeline for Design a test framework for validating static files
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 5, 2024 at 10:59 | history | edited | Doc Brown | CC BY-SA 4.0 |
Wording improved
|
| Jul 4, 2024 at 9:40 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 45 characters in body
|
| Jul 4, 2024 at 7:52 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 577 characters in body
|
| Jul 4, 2024 at 6:51 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 11 characters in body
|
| Jul 4, 2024 at 6:43 | comment | added | Doc Brown | @GregBurghardt: I guess the OP asks about a living code base. I would expect code which already exists, and code which will be written in the future. The existing parts are a probably a good basis for the missing requirements analysis, but might need some refactoring to make them unit testable. In the end, it does not really matter - even for a generic framework, one needs to have at idea what's going on with these JSON and XML files. Just "they are processed by some Python scripts" isn't enough. | |
| Jul 4, 2024 at 6:28 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 834 characters in body
|
| Jul 3, 2024 at 23:34 | comment | added | Greg Burghardt | Not to mention whether or not the Python scripts have already been written and the OP is trying to test them after the fact. | |
| Jul 3, 2024 at 22:40 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 17 characters in body
|
| Jul 3, 2024 at 22:34 | history | answered | Doc Brown | CC BY-SA 4.0 |