TestApp Installs a suite

[KristofKlein]

Hi,

another small test app questions. So I had the case, that a new test app was made, and got code, and also al:go found it and build it and published and said running tests now but never produced a result... I was quite puzzled what happened...and researched and found nothing.
So I want back to the code and started to remove all the things that are not "as it should be" based on the bing maps test app.... in the end I found Installation code that puts the codeunits into a test suite....and this was it! With that i also found an Issue here or bccontainerhelper stating the same....do not do that while installation of the test app...But the idea with the code was good: a developer might want to run the tests himself, in his local environment, and he does not want setup this again and again if the app installation flow can do that for him (and others).
Is there any idea such that Al:Go can be feeded with Suite Codes to run ? I mean the code for test does what: opens a page, sets an extensions id, waits for the codeunits to settle in the "DEFAULT suite" and runs them. (any idea why it does not utilize our codeunits? Just because it is setup in another Suite?).

[freddydk]

Back in the days - we asked people to write code to publish tests to a test suite.
That was changed some years ago - not sure why.
But... - I didn't think it would work.

Could you create a public hello world repo with the default apps and add your installation code so that it fails?
Then I will have a look and see if we can ignore the suite.

[KristofKlein]

I will see what I can do :)