Closed KPull closed 7 years ago
By the way, I think, in this case, we can get rid of all the descriptive texts we have in Bastion since they won't really be used for anything now. This includes Bastion.request(name, request)
and HttpRequest.name()
.
Merged in #87.
BastionRunner
, our JUnit Test Runner has turned out to be quite the letdown. A JUnit Runner needs to prepare a test completeDescription
to show in the IDE's GUI before the tests start to run. We wanted to show each Bastion call as it happened in the IDE's GUI but it appears we cannot do it.Also, poor documentation means that tests running using
BastionRunner
are causing bugs such as #49. I believe we should just get rid ofBastionRunner
for version 1.0 of Bastion since it's not worth the effort of maintaining for now.What does everyone else think?