• Form

• Table of contents
• SeleniumTests
  • QFQ-Test-Application
  • Preparation Tasks together with Enis
  • Update QFQ, Typo3, MariaDB and keep the tests up and running
  • Tasks for Shweta
  • Topics

SeleniumTests¶

• QFQ Selenium Test List

• Test QFQ
• Test a specific application

• Interactive Tests - used during developing of selenium tests
• Automated Tests -

QFQ-Test-Application¶

• Creating a dedicated QFQ-Test-Application (#17523) - this will be the base for all further interactice and automated tests.
• This will be the same for a) Developer (check out new features, example code) and b) selenium tests.
• The 'Develop' part will be based on the crose QFQ site http://webwork20:38773/
• Selenium Test Data: all tables start with 'Data_'
• Developer Test Data: all tables start with 'Dev_'
• The QFQ-Test-Application will be reinitialized nightly (to make clear that all changes are lost).
• When the QFQ-Test-Application has to be enhanced, a dump (T3, Data, Files) to the repository has to be done (so that the nightly init does not loose latest changes).

• Current Shweta 'QFQ learn' and 'Selenium test' is the same: http://webwork20:37091
  • We need a develop site for Shweta (might be the existing one, or a copy of the new QFQ-Test-Application)
  • A 'production' version which is 'QFQ-Test-Application'

Preparation Tasks together with Enis¶

• Setup dedicated QFQ test environment for run as automated tests (Check how Marc did it).
• Debugging & troubleshoot Python/Selenium tests - make it easier for Shweta to see what is not working and why.

Update QFQ, Typo3, MariaDB and keep the tests up and running¶

• Document how to update the QFQ-Test-Application.
• How does the developer fetch the latest QFQ-Test-Application?
• Later: Maybe several T3 / QFQ / MariaDB versions.

Tasks for Shweta¶

• Categorize Tests. E.g: Form, FormElement, Report, Link, Downloads
  • Create Wiki Pages for each category and write down basic tests (one per line) - go through https://qfq.io/doc.

• Define 'test-data': sql file, all tables have the prefix `Data_`, such test-data can be played (and should implicit remove all previous data).

Topics¶

• Clean Test Environment
  • Reproducable T3 QFQ Site
  • Reproducable Data

• Definition: What to test
  • Form
    • Form Save Record
    • Form Update Record
    • Form Delete Record
    • Each individual FormElement
    • Dynamic Update
  • Report
    • Syntax like: head, tail, shead, stail, rbeg, rend, renr, fbeg, fend, althead, altsql
    • `... as _link`
      • plain link
      • link with question dialog
      • link with tooltip
      • render mode

• Implement Tests

  *