We're updating the issue view to help you get more done. 

Smack integration test framework tries to instanciate abstract classes

Description

The IntegrationTestFramework tries to instanciate abstract test classes. This leads to a missleading number of avaliable tests. In the example below, there is one abstract class which is a test and another class which extends the abstract test.

 

As you can see, the abstract class is counted as part of the available tests.

This is not really a serious issue, but it may cause some confusion.

I believe the solution would be not to add abstract classes to available tests.

 

Environment

None

Acceptance Test - Entry

None

Assignee

Unassigned

Reporter

vanitasvitae

Labels

Expected Effort

Unknown

Ignite Forum URL

None

Components

Affects versions

Priority

Minor
Configure