org.eclipse.gmt.modisco.infra.query.tests
Class UnitTests

java.lang.Object
  extended by org.eclipse.gmt.modisco.infra.query.tests.UnitTests

public class UnitTests
extends java.lang.Object


Constructor Summary
UnitTests()
           
 
Method Summary
 void bug303036()
          
Methods inherited from class java.lang.Object
equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

UnitTests

public UnitTests()
Method Detail

test001

Throws:
java.lang.Exception

simpleEval

Throws:
java.lang.Exception

osgiReload

Tests that when the implementation of a Java query is modified, the new implementation is used instead of the old

Throws:
java.lang.Exception

oclQueryTest

Throws:
java.lang.Exception

oclQueryTest2

Throws:
java.lang.Exception

oclQueryTest3

Throws:
java.lang.Exception

emfmqQueryTest

Throws:
java.lang.Exception

jxpathQueryTest

Throws:
java.lang.Exception

installedQuery01

Using platform protocol to refer Ecore model.

Throws:
ModelQueryException

installedQuery02

Using http protocol to refer Ecore model.

Throws:
ModelQueryException

wrongName

Throws:
java.lang.Exception

wrongResultType

Throws:
java.lang.Exception

wrongScope

Throws:
java.lang.Exception

nullResultType

Throws:
java.lang.Exception

uniqueName

Throws:
java.lang.Exception

parameterUniqueName

Throws:
java.lang.Exception

returnType

The query declares that it returns EBoolean, whereas the implementation class returns an Integer

Throws:
java.lang.Exception

returnTypeMulti

The query declares that it returns a collection of EClass, whereas the implementation class returns a collection of Boolean

Throws:
java.lang.Exception

scope

The query declares EObject as a scope, whereas the implementation class defines EClass (which is more restrictive)

Throws:
java.lang.Exception

wrongNameInInstalledQuerySet


resourceSet

Throws:
java.lang.Exception

resourceSet2

Throws:
java.lang.Exception

resourceSet3


modiscoProtocol


bug303036

Bug 303036 - implements IJavaModelQuery may be done by a superclass

Throws:
ModelQueryException

wrongImplementationClassName

Throws:
java.lang.Exception

wrongImplementationClassInterface

Throws:
java.lang.Exception

bug306724

Bug 306724 - deleting a project containing a query set does not remove the query set from its catalog

Throws:
java.lang.Exception

bug307095

Bug 307095 - the validation state of a Java query is not updated when the Java class is fixed

Throws:
java.lang.Exception

bug307095v2

Bug 307095 - the validation state of a Java query is not updated when the Java class is fixed

Throws:
java.lang.Exception

bug307095v3

Bug 307095 - the validation state of a Java query is not updated when the Java class is fixed

Throws:
java.lang.Exception

bug307187

Bug 307187 - AbstractMoDiscoCatalog and name conflicts : If two querySets have the same name, only one will be registered in the catalog and the user will never be informed about this problem.

Throws:
java.lang.Exception

bug309657

Bug 309657 - Moving facet or query models generates wrong problem messages

Throws:
java.lang.Exception

bug310269

Check that a model stored in the catalog in contained in resource.

Throws:
java.lang.Exception

bug310599

Name conflict markers not cleared when closing or deleting other project

Throws:
java.lang.Exception

bug310599v2

Name conflict markers not cleared when closing or deleting other project

Throws:
java.lang.Exception