Timeline for Integration testing strategy for a volatile domain
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 20 at 13:51 | vote | accept | CommunityBot | ||
| Oct 11, 2024 at 9:22 | history | edited | Doc Brown | CC BY-SA 4.0 | Cites adapted to changes of the question |
| Oct 10, 2024 at 15:01 | comment | added | Greg Burghardt | @TomaszBąk: Regarding SDK size, you can still build in the ability to do A/B testing without deploying multiple SDKs to the same device. You could have a "developer" mode for the app so you can deploy the old and new SDKs side-by-side for testing purposes. You just don't want both SDKs deployed in the real production product downloaded by real end users. That way you can introduce additional logging and give the app to the other team. Have them read the logs and debug. | |
| Oct 10, 2024 at 11:11 | history | answered | candied_orange | CC BY-SA 4.0 |