A modern programming language that makes developers happier.

kotlinlang

I am using grpc spring server <https://github.com/LogNet/grpc-spring-boot-starter/blob/master/grpc-spring-boot-starter/src/main/java/org/lognet/springboot/grpc/GRpcServerRunner.java|https://github.com/LogNet/grpc-spring-boot-starter/blob/master/grpc-spring-boot-st[…]/src/main/java/org/lognet/springboot/grpc/GRpcServerRunner.java>
along with Spring extension
Seems like the server does not stop after test case is finished, leading to it getting reused for next test cases. :confused:

It will start stop per spec by default perhaps. You can control it. I'm not on a pc but check the docs it will be there

The thing is its not stopping after 1 springboottest spec is finished. I observed -
• the second spec still sees it
• second spring boot test is not started. I don’t see any spring startup logs or even debug point in @Configurations does get hit, meaning they are already hit. 
• debug points does not work for the second spec. 

So it's like the entire second spec is ignored

I'll send you a build scan when I'm on my work laptop.

the tests are failing due to the test case reusing the spring instance which was started by another test.

this seems to be not getting called. <https://github.com/LogNet/grpc-spring-boot-starter/blob/293597a16d9934d3fce94d3f4629b6c03389af65/grpc-spring-boot-starter/src/main/java/org/lognet/springboot/grpc/GRpcServerRunner.java#L175|https://github.com/LogNet/grpc-spring-boot-starter/blob/293597a16d9934d3fce94d3f46[…]/src/main/java/org/lognet/springboot/grpc/GRpcServerRunner.java>

DirtysContext fixes this. not sure if this should be proper workaround tho.

Are you using the spring listener or the spring extension ?