Excel Integration Testing

• Back

Summary

The following page documents testing of the Axpo Excel integration. Please note that Excel columns are written in brackets: i.e. "(AC)" is column AC in Excel document LinthalDrawing-Planning-1.xlsm.

Resources

Axpo Excel integration features are tested against the following specifications:

• requirements given in DrawMGT-AxpoExcelIntegration-15.pdf (Chapter 2)

• client-side implementation in DrawMGT-AxpoExcelIntegration-15.pdf (Chapter 4)

• use cases given in DrawMGT-AxpoExcelIntegration-15.pdf (Appendix A)

• Test notes at ExcelIntegrationToDoList#Testing

All tests against DrawMGT-AxpoExcelIntegration-15.pdf are performed with ExcelIntegrationAxpoDemoNotes in mind!

Critical Bugs

• Some client alerts inside Excel are wrapped in XML tags

• If "Create New Document" with title={any title}, Zugriff="E-[...]", Projektphase="1-[...]", Fachbereich="12.1-[...]", Objekt="101-[...]", Kontakt="111-[...]", Dokumenttyp="03-[...]", Laufnr.="0001", T0="24-12-11"; click "Save Selected".

• The following error is returned:

  <?xml version=\'1.0\' encoding=\'UTF-8\'?> <response type=\'Drawings\' key=\'drawingId\' id=\'\' ref=\'Doc\'> <error>Feld \'Dok. Nr.\' \'Objekt\' muss angegeben werden.</error> <error>Feld \'Dok. Nr.\' \'Kontakt\' muss angegeben werden.</error> <error>Feld \'Dok. Nr.\' \'Dokumenttyp\' muss angegeben werden.</error> <error>Feld \'Dok. Nr.\' \'Laufnummer\' muss angegeben werden.</error> <error>Feld \'Dok. Nr.\' ist ung?ltig.</error> </response>

• FAILED: I expected a meaningful alert but got a meaningless alert (wrapped in XML).

• Vorabzug Flag handling / RevC Revision Type menu handling:
  • onChange RecC Revision type behavior (CD):
    • gut zur Ausführung: sets to keyRefCTypeId = 15 -- OK
    • Freigegeben: sets to keyRefCTypeId = 13 -- OK
  • onChange Vorabzug behavior (AP):
    • ja:
      • Vorabzug fields are locked -- FAILED
      • after save:

        • revBVorabzugFlag => 1 -- OK

        • menu static: -- FAILED
        • Vorabzug fields are locked -- FAILED
      • revision code changed: -- FAILED
    • nein:
      • Vorabzug fields are unlocked -- OK
      • after save:
        • menu static: -- FAILED

        • revBVorabzugFlag => 0 -- OK

        • Vorabzug fields are locked -- FAILED
      • revision code changed: -- FAILED

• FAILED: When Vorabzug fields are 'locked', it's still possible to enter data and select from select menues. Also, if I change the Vorabzug flag, the revision code is not changed.

• "Search Document" -> Out-of-range data causes funny results:

• FAILED: Because it is possible to enter out-of-range data in Excel's select menues, the database queries are mixed-up and funny results are produced and placed in the worksheet.

• If T0 (CS) is set/updated and "Save Selected", calculated plan dates are not saved on the server:

• FAILED: Calculated designPlanDate (BQ) & checkPlanDate (BX) are not saved server-side.

• If I change Gruppe (T) - Gruppe (ignored?) -- FAILED
  • TODO be more precise ...
• Update GA/Freigegeben menu and "Save Selected"

• FAILED: updates of GA/Freigegeben menu (CD) are not saved on the server-side.

Minor Bugs

• Umlauts may still not be rendered correctly. The final test of this is possible only after all alerts are displayed correctly being not wrapped in XML anymore.

• "Search Document" -> Label 'Objeckt' should say 'Objekt'

• "New Document" -> Dokumenttitel 2 should be 'Titel-2'

Amendments

• Excel select menues allow to enter data. It would be more user-friendly when there would be a client-side check for invalid data input (i.e. display alert when "Search Documents" Rapport="{invalid-value}").