Timeline for How to control time with API testing?
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 29, 2020 at 14:48 | vote | accept | Shoe Diamente | ||
| May 29, 2020 at 9:05 | comment | added | Shoe Diamente | @Flater That's true. But following the exact definition makes blackbox testing basically impossible (it's possible as you said by waiting X amount of time but that's reasonably impossible when you have to wait days and you only have 1 hour to verify that your code works). | |
| May 29, 2020 at 9:03 | review | Close votes | |||
| Jun 13, 2020 at 3:06 | |||||
| May 29, 2020 at 9:02 | comment | added | Flater | Using the system clock is an implementation detail. Knowing that the system clock is being used is knowing an implementation detail. | |
| May 29, 2020 at 9:01 | comment | added | Shoe Diamente | @Flater Well, for example simulating the system clock would not "change implementation details of the API" but change the system the API runs on. | |
| May 29, 2020 at 8:59 | comment | added | Flater | There is a contradiction between your question (how to control the clock) and your explanation of blackbox testing (not being able to mock/change implementation). I've already written up an answer to address both black and white box testing. | |
| May 29, 2020 at 8:57 | answer | added | Flater | timeline score: 3 | |
| May 29, 2020 at 8:56 | answer | added | l0b0 | timeline score: 0 | |
| May 29, 2020 at 8:49 | answer | added | Ewan | timeline score: 1 | |
| May 29, 2020 at 8:44 | comment | added | Shoe Diamente | @Flater Blackbox testing of an API. Testing as if you didn't know the implementation details of the API and therefore not being able to mock or change them. | |
| May 29, 2020 at 8:42 | comment | added | Flater | What do you mean by "from an external point of view"? | |
| May 29, 2020 at 8:41 | history | asked | Shoe Diamente | CC BY-SA 4.0 |