Story #95949
closed
Split functional test extensions into smaller pieces
Added by Anja Leichsenring about 3 years ago.
Updated about 2 years ago.
Estimated time:
(Total: 0.00 h)
Description
We got a few test extensions that functional tests use for several purposes, and those have grown out of hand. Some restructring is necessary for easy writing and maintaining functional tests.
- Status changed from New to Accepted
Naming things:
MM (Marta-Marta) vs. MN (Marta-Norbert):
MM is the 'classic' MM table with uid_foreign and uid_local as known from select/group types. The MM table has no TCA.
MN is special for inline, where the MN table has TCA.
"sym" means "symmetric" - a mm/mn relation to itself.
"asym" means "anti symmetric" - a mm/mn relation from one table to a different table.
"attr" is for "attribute" - When the MN table has additional fields like a "stars / quality" selector in a hotel<->offer relation, or even a "price" inline attached to the MN relation in a hotel<->offer relation.
Renamings:
Scenario tables tx_irretutorial_mnmmasym_* are extracted to ext:test_irre_mm
Scenario tables tx_irretutorial_mnsym_* are extracted to ext:test_irre_mnsymmetric
Scenario tables tx_irretutorial_mnasym_* are extracted to ext:test_irre_mnattributeinline
Scenario tables tx_irretutorial_mnattr_* are extracted to ext:test_irre_mnattributesimple
Scenario tables tx_irretutorial_1ncsv_* are extracted to ext:test_irre_csv
Scenario tables tx_irretutorial_1nff_* are extracted to ext:test_irre_foreignfield
- Status changed from Accepted to Resolved
I think we're done here for now.
- Status changed from Resolved to Closed
Also available in: Atom
PDF