search

eMoflon / benchmarx

Infrastructure for implementing benchmarx: benchmarks for bidirectional transformation (bx) tools. Also contains a collection of example benchmarx and test runners for various and diverse bx tools.
GNU General Public License v3.0
9 stars 12 forks source link

Save models after transformations #45

Closed tsdh closed 7 years ago

tsdh commented 7 years ago

I just started writing my solution and so far I can run it using JUnit. However, 19 test cases fail and it is hard to tell what's the problem. In the "Failure Trace" view I can see some textual representation of the model the test expected and what it actually got. However, that's not too easy to interpret.

Would it be possible to change the framework to call the saveModels(String name) method after each transformation so that we can inspect the results afterwards?

In my case, I save the models there and also print some PDF visualizations. It would also be nice to get a handle on the expected model so that I can print that, too, for comparing it with the actual result model.

anthonyanjorin commented 7 years ago

Hi Tassilo,

just to make sure I understand your suggestion before I start making wild changes...

Why don't you do what you want to do in your implementation of the assertPrecondition and assertPostcondition methods of your tool? Even if you're extending BXToolForEMF you could still wrap some extras around a super call.

Would that work? In those methods you have access to both actual and expected models.

Cheers, Tony

tsdh commented 7 years ago

Ah, I haven't seen those and I guess that'll work. I'll report back is that's the case or not. However, probably I won't be able to work on the case until next weekend.

tsdh commented 7 years ago

Ok, tried that and it works ok. So no changes needed. Thx!