[PATCH 2/7] d3d11/tests: Port test_create_texture2d() from d3d10core.

[Henri Verbeet]

On 10 August 2015 at 11:01, Józef Kucia <joseph.kucia at gmail.com> wrote:
> The implementation of D3D11CreateDevice could be delayed until these tests
> pass. ID3D11Device could still be exposed through ID3D10Device. However, it
Yeah, but you'd still basically have the same issue. I.e., when you
make create_device() work in some way, you'd have to adjust all the
tests because e.g. ID3D11Device_CreateTexture2D() returns E_NOTIMPL.

> How should be approached other tests which potentially influence decision
> how to organize D3D10 and D3D11 code? For example, tests which check
> implemented interfaces for D3D11Device. Is it preferred to submit them
> before implementation?
I have no particular preference either way, but in principle it's fine
to submit those before the implementation.