for the first the tests aren t nested and so when they start

Question

for the first the tests aren t nested and so when they start to repeat through the inner loop on the second outer loop I get duplicate test name errors but if I create that test internally now there are two tests with that name Here is a demonstration of the issue by just adding a prefix to the test

sam · Answer

Can you paste up the code for the first example

sam · Answer

save me typing it all out

snowe · Answer

```class PrintDrlTest FreeSpec test forAll a b c outer gt forAll 1 2 3 inner gt println $outer$inner test 2 forAll a b c outer gt prefix $outer forAll 1 2 3 inner gt println $outer$inner ```

snowe · Answer

I m on 4 4 1

sam · Answer

Ah ok I see

sam · Answer

Take this part

sam · Answer

``` test forAll a b c outer gt forAll 1 2 3 inner gt println $outer$inner ```

sam · Answer

that s just two nested loops and the outer loop won t be joined with the inner loop for a test name

sam · Answer

like it looks like the tests will be nested but they won t be because you re not creating inner tests

sam · Answer

It s no difference to going ```test a test 1 test 2 test b test 1 test 2 ```

snowe · Answer

for either of those they re not really nested How do I get them to nest then I tried `test 2` without the prefix and have the issue of the duplicate top level tests

snowe · Answer

see my most recent pictures in the main channel

sam · Answer

If you want to nest tests then just roll your own loop

sam · Answer

``` test listOf a b c forEach outer gt $outer listOf 1 2 3 forEach inner gt $inner println $outer$inner ```

snowe · Answer

what does the forAll accomplish then If it needs to be nested in a test to begin with and you can t nest them without this issue

sam · Answer

forAll is special syntax that will create tests for you basically doing what I pasted above

snowe · Answer

yes I realize that

snowe · Answer

just seems like it should work to nest as well I ll just roll my own loop

sam · Answer

nested tests are created at runtime because it s just nested lambdas right So when the code is compiled with forAll it binds to the closest statically created test loop so in your example the closest loop is the top level test block The inner block doesn t exist until runtime

snowe · Answer

oh that makes sense alright thanks

sam · Answer

I can see why it s not intuitive Let me make a ticket to see if we can make the whole thing defer until runtime

sam · Answer

snowe · Answer

awesome thanks for that

sam · Answer

thanks for the feedback always good to keep improving things

snowe · Answer

welcome I was just really confused by it all couldn t understand why it was making the top ones twice

sam · Answer

Wasn t obvious to me either at first lol