Question about use of "Mock" in the TODO sample app – but no test project? #19815
-
Hi there, However, I couldn't find any dedicated test project in the solution, which confused me a bit. Normally, I would expect mocks to appear in the context of unit or integration testing, typically in a separate test project. I also looked into the Uno Platform documentation regarding mocks, but I only found references in the contributing section, specifically in the context of tests – which aligns with the typical definition and usage of mocks in testing. So I'm wondering: how should I understand the presence of these "Mock" classes when there's no test project? Are they intended for something like manual testing, design-time previews, or maybe early development scaffolding? If there is an explanation in the docs and I simply missed it, I’d really appreciate a link or pointer to the right section – I’d love to learn more about the intended pattern here. Thanks in advance! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I think the purpose of these mock classes is to provide a fake implementation of a "server" to work with the data - to simulate how the app would behave when running against an actual server, even though it is just for demonstration purposes. A better name for these would probably be |
Beta Was this translation helpful? Give feedback.
I think the purpose of these mock classes is to provide a fake implementation of a "server" to work with the data - to simulate how the app would behave when running against an actual server, even though it is just for demonstration purposes. A better name for these would probably be
Stub
orInMemory