1.2.0
Test Coverage (1.2.0)
| Name | Coverage (%) | Covered Lines | Coverable Lines |
|---|---|---|---|
| RestServer.DefaultRequestHandlerImpl | 68.4 % | 13 | 19 |
| RestServer.Endpoint | 100.0 % | 3 | 3 |
| RestServer.EndpointCollection | 100.0 % | 83 | 83 |
| RestServer.Helper.HeaderBuilder | 100.0 % | 26 | 26 |
| RestServer.Helper.UnityNetHelper | 100.0 % | 6 | 6 |
| RestServer.LowLevelHttpServer | 76.9 % | 10 | 13 |
| RestServer.LowLevelHttpSession | 77.7 % | 28 | 36 |
| RestServer.RestRequest | 88.4 % | 69 | 78 |
| RestServer.RestServer | 88.8 % | 48 | 54 |
| RestServer.SpecialHandlers | 100.0 % | 6 | 6 |
| RestServer.ThreadingHelper | 100.0 % | 49 | 49 |
Average: 90.9%
The missing methods to 100% are usually rare error handling code, like socket errors or other low level functionality.
Profile Marker (1.2.0)
Profile markers can be assigned when scheduling a workload via ThreadingHelper.Instance.ExecuteXXX methods like this
ThreadingHelper.Instance.ExecuteAsync(() => {
transform.position += new Vector3(0.001f, 0.001f, 0.001f);
}, "Position Updates");
These can now be found inside the profiler
By default, the name of the execute method (e.g. ExecuteSync) is used as the profile marker name.