Describe the bug
When creating an operation type, Aquarium creates code objects for the protocol, documentation, preconditions, and cost model.
As part of enabling people to run tests from pfish, I added in a step to create a test file (In the operation type controller). The test file is not visible in the Aquarium interface (it’s distinct from the tests under the test tab), but it can be pulled with pfish.
This is causing an error message to appear when creating a new operation type using the interface. The operation type gets created, but an error message pops up.
As you can see from the request, there should be an entry for “test” here, but there isn’t.
To Reproduce
Steps to reproduce the behavior:
pull the pfish-compatibility-updates branch and run aquarium.
Go to the developer page in Aquarium and hit new to create a new op type.
Give the op type a name and hit save.
After getting the error message, refresh the page to see that the new op type was saved.
Expected behavior
There should not be an error message.
marikoja
commented
4 years ago 
Describe the bug When creating an operation type, Aquarium creates code objects for the protocol, documentation, preconditions, and cost model.
As part of enabling people to run tests from pfish, I added in a step to create a test file (In the operation type controller). The test file is not visible in the Aquarium interface (it’s distinct from the tests under the test tab), but it can be pulled with pfish.
This is causing an error message to appear when creating a new operation type using the interface. The operation type gets created, but an error message pops up.
As you can see from the request, there should be an entry for “test” here, but there isn’t.
To Reproduce Steps to reproduce the behavior:
Expected behavior There should not be an error message.
Screenshots
Error Message
Created OT
Request