Refactoring #1291

Feature #1290: === Core: framework ===

core functional test machinery: simplify, or at least explain

Added by wuttke over 3 years ago. Updated over 3 years ago.

Status:ResolvedStart date:27 Apr 2016
Priority:NormalDue date:
Assignee:wuttke% Done:

100%

Category:-Estimated time:17.00 hours
Target version:-

Description

I find it hard if not impossible to understand the functional test machinery.

It's already somewhat tricky at CMake level, and then there come several layers of C++.
We have core_functional_tests, CoreFunctionalTest, and CORE_FUNCTIONAL_TEST: how do they relate to each other?
At the very least, we need more explanations in the code.
Also, reconsider renaming some files/classes/functions.
UPPERCASE_NAMES are conventionally reserved for preprocessor macros - why use them for an ordinary function?


Subtasks

Refactoring #1422: provide clue when test failsResolvedwuttke

Bug #1452: PySuite tests fail when executed in parallelResolvedwuttke

History

#1 Updated by pospelov over 3 years ago

  • Status changed from New to Sprint
  • Target version set to Sprint 31

#2 Updated by wuttke over 3 years ago

  • Assignee set to wuttke

#3 Updated by wuttke over 3 years ago

By now resolved:
  • CMake machinery simplified
  • Uppercase C++ functions merged into *Suite.cpp
Still to investigate:
  • Can C++ component registry be simplified

#4 Updated by wuttke over 3 years ago

  • Status changed from Sprint to Backlog
Mostly done. Still TODO:

#5 Updated by wuttke over 3 years ago

  • Target version deleted (Sprint 31)

#6 Updated by wuttke over 3 years ago

  • Status changed from Backlog to Sprint

Last open subissue resolved in 6f660da3

#7 Updated by wuttke over 3 years ago

  • Status changed from Sprint to Resolved

Also available in: Atom PDF