> On 15 Sep 2016, at 18:38, Ben Coman <[email protected]> wrote:
>
> In a freshly downloaded build 60224, I open TestRunner and run all
> tests. At run 418 I get a dialogue asking for the Author. To me that
> seems wrong. I don't want any code changes made during testing to
> have my normal identification on them. Tests invoked from Test Runner
> should be author-tagged something like 'TestRunner' or
> 'TestRunner-BenComan'.
>
> The question arises in this particular case due to...
> RPackageMonticelloSynchronisationTest >> setUp
> ...
> Author fullName ifNil: [ Author fullName: 'Tester' ].
>
> Minor point... this check actually is a bit pointless since #fullName
> invokes #requestFullName that presents the dialog. And #fullName will
> *never* return nil. At a minimum it returns 'Anonymous'.
>
> First step would seem to be wrapping TestCase>>runCase:
> with Author useAuthor: 'TestRunner' during: [ .... ]
>
Yes, something like this this would be good.
> But further. I envisage a time when TestRunner doesn't block the UI,
> so I can happily browse around the system and code while TestRunner is
> doing its thing. Obviously the system is not set up to have two
> parties (myself and TestRunner) both updating code in the system, but
> changing the state of the global Author uniqueInstance like this…
>
Yes, Nautilus used to fork running tests… leads to lots of strange problems.
>
> would itself seem to a big impediment. It would be good if "Author"
> was dependent on the context of the call chain. This would seem a
> requirement for one day having two people working in the one Image (is
> this a possible use case where someone is using a remote debugger
> while another person is using the standard UI?)
>
Could it be part of Denis new ExecutionEnvironment concept?
Marcus
