Feature #8256

Add tests for EMG failures

Added by Ilja Zakharov 5 months ago. Updated 28 days ago.

Status:ResolvedStart date:06/23/2017
Priority:UrgentDue date:
Assignee:Ilja Zakharov% Done:

0%

Category:TestingSpent time:-
Target version:0.3
Published in build:

Description

There are several unsolved and quite complex problems when EMG cannot generate an environment model or generates it incorrectly. It is proposed to develop a test suite that would allow checking typical problems after new EMG improvements. Most of these problems occur due to complicated use of type definitions, type and function scope, function pointers, etc.

History

#1 Updated by Evgeny Novikov 5 months ago

  • Category changed from Environment model to Testing

#2 Updated by Evgeny Novikov 3 months ago

  • Target version set to 0.3

#3 Updated by Ilja Zakharov 29 days ago

  • Status changed from New to Resolved

Instead of doing tests I fixed failures itself. Gladly because we decided to disable patterns in EMG it was not too difficult. Implemented in 'emg-failures'.

#4 Updated by Alexey Khoroshilov 29 days ago

Ilja Zakharov wrote:

Instead of doing tests I fixed failures itself. Gladly because we decided to disable patterns in EMG it was not too difficult. Implemented in 'emg-failures'.

What do you mean by "disable patterns in EMG"?

#5 Updated by Ilja Zakharov 29 days ago

What do you mean by "disable patterns in EMG"?

Since March we do not call callbacks if no interface specification is given.

#6 Updated by Alexey Khoroshilov 29 days ago

You should add "by default". It is an important feature of EMG for some of our use cases.

#7 Updated by Evgeny Novikov 28 days ago

I merged that branch into tests.

Also available in: Atom PDF