Story #13995

[Controller] Port "collection update" functional tests from Rails API to controller test suite

Added by Tom Clegg about 3 years ago. Updated 3 months ago.

Assigned To:
Target version:
Start date:
Due date:
% Done:


Estimated time:
Story points:


Port enough tests that we can then move the "update collection" functionality into the controller and be confident the resulting system still works.
  • Rails functional tests
  • Rails integration tests
  • Some permission checks from the Rails unit tests ("only admin can do xyz")

We don't need to port all of the unit tests -- most of that should wait until we know what the units look like in Go. Focus on proper API request handling more than the underlying collection model behavior.

Since these APIs are (for now) implemented by proxying to Rails, the test can't rely on rolling back an entire-test transaction to avoid side effects. (It should be enough to call the "database reset" API in test teardown.)

Related issues

Related to Arvados Epics - Story #9053: Port API server to GoNew06/01/202212/31/2022

Blocks Arvados - Story #13997: [Controller] Port "collection update" API from RailsNew


#1 Updated by Tom Clegg about 3 years ago

#2 Updated by Tom Clegg about 3 years ago

  • Blocks Story #13997: [Controller] Port "collection update" API from Rails added

#3 Updated by Peter Amstutz 3 months ago

  • Target version deleted (To Be Groomed)

Also available in: Atom PDF