[Test] Allow defining types or contracts locally in the test file itself

[satyamakgec]

if I import a contract in a test file, it would not be able to resolve as it needs to be added in configuration, but it would not be possible as it is a static code written in the file itself.
ex -

foo.cdc <--- test file name

// Below are the contents of the foo.cdc
import Test
import Bar from ./Bar.cdc

fun setup() {
 ...
}

fun testFoo() {
   Bar.Abc()
}

.... End of Foo.cdc

// Below are the contents of Bar.cdc
pub contract Bar {
   pub struct Abc {
     ...
   }
}

In the above example I can't use Bar.Abc data type directly in the tests as I can't import the Bar in the Foo.cdc because of the configuration problem.

[franklywatson]

@satyamakgec can you illustrate how you have had to workaround this in https://github.com/onflow/Offers/tree/offers-implementation/lib/cadence/test and what you would expect for desired way of handling this?

[SupunS]

You would have to define each contract in a separate file of its own (same as running in emulator/testnet/mainnet). i.e:

foo.cdc script

import Test
import Bar from ./Bar.cdc

fun setup() {
 ...
}

fun testFoo() {
   Bar.Abc()
}

Bar.cdc

pub contract Bar {
   pub struct Abc {
     ...
   }
}

I assume all projects already have contracts defined in separate files, so I'm curious/ like to know more about the exact use-case to have them defined in the test-file itself?