Sorry for responding so late!
I haven't gotten around to doing the move, but the target is created. I suspect that the path of least resistance for you is to keep adding the tests to content, but you're welcome to try adding them to storage instead!
The only two files left in content_unittests are listed below. They'll be more difficult to move.
blob/blob_transport_host_unittest.cc
- uses content/public/test/test_browser_thread_bundle.h
fileapi/file_system_operation_runner_unittest.cc
- uses content/public/test/test_browser_thread_bundle.h and content/public/test/test_browser_thread.h
On the mechanical side, all the test stuff that got moved is in the content namespace, and needs to be moved to the storage namespace.
The files in storage/browser/test are used by content/, chrome/, and possibly extensions/. They should probably be renamed together, because the CLs will require broader reviews. Everything else can be renamed in reviews that go to storage/ OWNERS.
Comment 1 by bugdroid1@chromium.org
, Oct 11 2016