Peaky discovers tests in an application and maps routes to allow them to be called over HTTP. These tests can live within the application they are testing or stood up as their own service.
One of the great benefits of Peaky is moving tests away from the antiquated paradigm where tests are ran on local machines to being ran from a sharable and accessible location. This does away with ‘works on my machine’ test issues and allows you to easily share, discover, and execute tests.
Peaky also provides users with a CDN hosted UI out of the box with hooks to provide your own UI experience if you desire.
Peaky aims to remove the barriers between production and pre-production environment tests. With Peaky you register your target environments and their dependencies and let Peaky inject the correct dependency for each test. E.g. a tests that verifies a homepages availability needs to only be written once and depending on the request to Peaky, it can be ran against any target.
Basically any public method on concrete types derived from IPeakyTest. There are a few exceptions to this. Peaky will not expose the following as tests:
- Public properties
- Constructors
- Methods with non-defaulted parameters
- Methods with a Special Name
Peaky will also discover Its.Log Sensors in all loaded assemblies and expose them via HTTP endpoints.