AludraTest Roadmap

This page collects all ideas for upcoming AludraTest versions; these may be new features as well as "things we do not like and have to change somehow". Feel free to add new items to the lists.

AludraTest 3.0

New Features

• "Tags" for test cases (e.g. Annotation based); execution selection based on tags (e.g. "UI" AND NOT "Draft"), see https://github.com/AludraTest/aludratest/wiki/Draft-for-Filter-Category-based-Test-Execution. ==> DONE

Changes

• DataMarkerCheck class should not be used in a static way. Currently, init() call is required. ==> REJECTED - is used in a static style - as utility function by many classes not totally under AludraTest control (e.g. validators). Still, configuration is important, which is only dynamically provided. So we will have to keep it this way for a while...
• Component objects should not be instantiated (new()) from testing code (UIMaps). There should be some factory pattern applied which would allow for using IoC also within Component classes. This would require a massive amount of refactoring in client code. ==> DONE

AludraTest 3.1

New Features

• Annotations for Resources, @Resource analogous to @Source; Framework instantiates resources and monitors their usage, identifies deadlocks. Resource Manager can plan resource allocation (e.g. startup a VM)
• Download support for files etc. from Selenium Service ==> DONE
• SVN Service ==> POSTPONED

Changes

• log4testing.xml configuration is outside the overridable configuration mechanism. Perhaps there is a way to extend the configuration mechanism to allow XML config files as well.