add a test

Author: baggepinnen

docs/src/batch_linearization.md

@@ -219,6 +219,10 @@ plot(
 )
 ```
 if we open at both `y` and `v` or we open at `u`, we get controllers for the different values of the scheduling variable, and the corresponding measurement feedback (which is the same as the scheduling variable in this case).
+```@example BATCHLIN
+using Test
+@test all(sminreal.(controllersv) .== sminreal.(controllersu))
+```
 
 However, if we only open at `y` we get controller linearizations that _still contain the closed loop through the scheduling connection_ `v`. We can verify this by looking at what variables are present in the input-output map
 ```@example BATCHLIN
@@ -248,6 +252,5 @@ Batch linearization in multiple different operating points is an intuitive way t
 
 
 ```@example BATCHLIN
-using Test
 @test sol(6.99, idxs=closed_loop.duffing.y.u) ≈ 0.0 atol=0.01
 ```