Even though it's already required. I think this may be something to do with it executing the Ext.create when it's parsing the markup before the requires can be assessed. Is there any way of structuring a test so that this no longer gives a warning?
Hm.. Yes, the warning is probably from there. Do you have the `Ext.define()` call at the top-level scope of the test file? Moving it inside the `StartTest()` scope should fix this I think.
Here you create an instance of the `MyApp.template.MyTemplate` at the time of the `Ext.define('MyApp.column.MyCol'` call. The loading, that is initiated by the `requires: ['MyApp.template.MyTemplate']` is asynchronous, so, the only way to create that instance is to load the class synchronously, hence the warning. To avoid the warning, you need to `Ext.create('MyApp.template.MyTemplate')` at some later point, inside the constructor for example.