Allow access to virtual objects for testing purposes

Product name

Can apply for every product with API integration, especially on Nuki Combo

Summary

It’s actually hard to create new features and test feature already made when objects are in use for business. Eg., we have a Nuki Combo Smartlock in a place used by customers. When we’re testing the lock/unlock script, we need to provide a smartlock_id for Nuki to responds our test with success or not. This lead to the door being lock and unlock, which is not very great for security.

Features

Multiple virtual objects with ID that can have the same behavior than real objects, so we can send request to the API and have responses without the mechanical part of the object, and so, without any undesired behavior.

Reason

Every developers write test and try features. This will improve our ability to write tests in our app and also scale faster and cheaper (because for now, we need to buy objects for testing purpose only…)

Examples

  • Unit and integration testing
  • Implement new features
  • Prevent issues at scale by testing multiple request at the same time on multiple objects
  • Improve performances

What do you think about that? Is there any other people have those needs?

Thanks you!
Anthony