If .al (object) file is in edit mode (not yet saved) TestScriptor cannot not be in sync

[lvanvugt]

Can we make TestScriptor to ask user to save file first?

[DavidFeldhoff]

What do you mean? So the .al file is in a dirty state (=has changes), but on the UI I change some element? And then there should be a question if the user wants to save the file first?

[lvanvugt]

Yes!

[DavidFeldhoff]

Hm.. would be possible. But when should that happen? If he selected the scenario?

I think it would be better if we just get the current (maybe dirty) content of the file on selecting the scenario. And if the user edits the current scenario, then the ATDD could be updated - Then the ATDD is always in sync.

But I don't know how much work that would be for Marton.. but I think that would be the better solution

[DavidFeldhoff]

Hm.. would be possible. But when should that happen? If he selected the scenario?

I think it would be better if we just get the current (maybe dirty) content of the file on selecting the scenario. And if the user edits the current scenario, then the ATDD could be updated - Then the ATDD is always in sync.

Unfortunately I don't know how much work that would be for Marton. Could be that that change won't be that easy.. but I think that would be the better solution

[lvanvugt]

Makes sense.

@martonsagi ?