Error: Macro BackLinksMenu(None) failed

compressed data is corrupt

Error: Macro TicketQuery(summary=PLATFORM_STANDARDS_AUTO_TESTS_R1, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed

current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

The aim of this revision of the task is to improve the auto testing infrastructure, conventions etc.

Task requirements

• improve the standards for Unit Tests:
  • there are classes for which unit tests are compulsory.
  • there are classes for which unit tests are impossible and the least it can be done is integration test.
  • Note: stating the classes that should be unit tested can be done by component and team they belong to.
• provide more information about the javadoc of unit tests:
  • should it be compulsory or not.
  • how descriptive should it be - after all these are only tests and are not supposed to be reused.
• improve the conventions of unit tests. integration tests etc.
  • it is more suitable to provide information in the wiki instead of links to wikipedia.
• review the helper classes and provide more if necessary.
  • make sure that assertions are enabled for unit tests.
  • provide helper classes for UI testing.
    • either provide a convenient way for testing the UI.
    • or propose a UI testing library - such libraries are already researched some time ago and these include: Abbot, !UISpec4J, JFCUnit.
      • new libraries may have appeared since then.
      • these may have been improved for the time passed.

Task result

• wiki page.
• source code.
• new jars or other resources.

Implementation idea

• review the PLATFORM_STANDARDS_AUTO_TESTS
  • add more info as stated in the requirements section.
  • review written things up to now.
• research for libraries for GUI testing.
• if no result from the research:
  • think of a way to test the GUI with minor source code re-factoring and more helper things.

Related

PLATFORM_STANDARDS_AUTO_TESTS is the document where more information should be provided and unnecessary information removed. PLATFORM_STANDARDS_AUTO_TESTS_R1

How to demo

• open PLATFORM_STANDARDS_AUTO_TESTS and read the information provided.
• everything new in for testing should be provided there.

Design

Implementation

Testing

Comments

Rules should be like checklist like in other platform standards (this is related to reviewing) How-tos should be linked and added for auto tests.