Timeline for Simulating different times of day when running integration tests, .NET/XUnit
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 16 at 21:42 | history | protected | gnat | ||
| Apr 16 at 20:32 | answer | added | Green Grasso Holm | timeline score: -1 | |
| Apr 15 at 23:53 | comment | added | Steve Jessop |
For example if the reason is that you don't know how to enforce for the future a rule on your project like, "Never call DateTimeOffset.Now, call this instead", then maybe someone would offer help with enforcing the rules they're proposing.
|
|
| Apr 15 at 23:50 | comment | added | Steve Jessop | Do you really need the constraint "Without completely overhauling the entire existing application to use some library in place of all the existing invocations of DateTime.Today and DateTimeOffset.Now,", as in you don't want to search and replace through the code base? I ask because all the answers you're getting, except that gnasher729 said "you might be successful having the linker substitute an alternative", are assuming you don't actually need the constraint. Which might be a legitimate challenge to your premise, but if you really need it you should explain why. | |
| Apr 15 at 23:01 | history | became hot network question | |||
| Apr 15 at 22:37 | answer | added | Arseni Mourzenko | timeline score: 5 | |
| Apr 15 at 17:12 | answer | added | DavidT | timeline score: 0 | |
| Apr 15 at 15:50 | answer | added | gnasher729 | timeline score: -1 | |
| Apr 15 at 15:15 | review | Close votes | |||
| Apr 20 at 3:00 | |||||
| Apr 15 at 14:56 | answer | added | Ewan | timeline score: 3 | |
| S Apr 15 at 14:49 | review | First questions | |||
| Apr 15 at 15:49 | |||||
| S Apr 15 at 14:49 | history | asked | Green Grasso Holm | CC BY-SA 4.0 |