Refactoring in TTS-NG (#3)

Andrzej Wójcik (Tigase) opened 9 years ago

Due Date
2016-07-16

Currently we have all test cases named as TestXXX where XXX is task number. This was ok, however now when we create common test cases they should be named properly so we could easily find test in IDE.

Things to do:

put existing tests in packeges (ie. pubsub, http, etc.)
if tests are common rename test classes

Activities

Wojciech Kapcia (Tigase) commented 9 years ago

Please keep in mind projects depending on TTS-NG and it's classes.
Andrzej Wójcik (Tigase) commented 9 years ago

I've changed name of test classes and changed XML - splited testng.xml so now each component has it's own test suite.

This should make it easier to find issues and easier to find in which component we have an issue.

%wojtek I renamed test classes and splited XML, so it may be required to update clients tests projects. However it will need to be done after we update clients test projects to use never version of TTS-NG as my changes will be in @1.1.0-SNAPSHOT@.

Please check if my changes are OK or if you would like some additional changes to TTS-NG to be done.
Wojciech Kapcia (Tigase) commented 9 years ago

Changes looks ok. One thing I would consider is adding a global xml file linking to all sub-xml groups (if that's possible).

Other than that, we only need to keep in mind to update the depended projects after releasing tts-ng-1.0.0 (or we could simply make them use this final version)
Andrzej Wójcik (Tigase) commented 9 years ago

%wojtek As I cheked it is not possible to use single XML file to link subgroups.

As there is nothing more to do in this task I'm closing it.
Login to comment

Type	Task
Priority	Normal
Assignee	Andrzej Wójcik (Tigase)
RedmineID	4346

Issue Votes (0)

Watchers (0)

Reference

tigase/tigase-tts-ng#3