[WIP] Studio library view tests

Essentially it's a parameterized test. It might make sense to actually make it parameterized, for the benefit of knowing exactly what data failed the test. Since `nose` is widespread in edx-platform tests, there's a really convenient package `nose-parameterized` that allows creating parameterized unit tests with just a decorator around test method, omitting all the boilerplate methods vanilla `nose` suggests to use.

I don't think `nose-parameterized` have already been usedin edx-platform, so the use of third-party lib in edx-platform when similar functionality ave already been achieved without it is a debatable question, so it's up to you to decide.