Ticket #1259 (new enhancement)

Opened 12 months ago

Last modified 10 months ago

Enhance Testing Tools test result data

Reported by: Matti Tahvonen Owned by: Matti Tahvonen
Priority: undefined Milestone: IT Mill Sponsored Backlog
Component: undefined Version: 5.0.0-pre
Keywords: Cc:
Known Issue description:
Hours estimate: Deadline (dd.mm.yyyy):
Known Issue version (since): Known Issue title:
Hours done: Depends to:
Affects documentation: no
Known Issue workaround:
Affects release notes: yes Contract:

Description (last modified by Matti Tahvonen) (diff)

Now contains:

  • test case id
  • success
  • exceptions
  • asserts

[X] = done

Test result data should contain:

  • [X] versions
    • [X] Application (set to Application object, need to build JS interface to fetch it)
    • [X] Toolkit (need to build JS interface for quering it)
    • [X] Browser (TT can fetch this
  • [X] executed script ( script may change, so either executed or if versioning is implemented - revision number)
  • server side exceptions (if easily done)

Some extra ideas:

  • Document.innerHTML
  • Previously received UIDL:s (as text)
  • Previous variable-changes sent (as text)

Change History

Changed 12 months ago by Matti Tahvonen

  • description modified (diff)

Changed 12 months ago by Matti Tahvonen

  • hours_left changed from 12 to 4
  • description modified (diff)

in [3537] scripts are "versioned" (in own table) and id is saved to results. Yesterday implemented versions.

Changed 10 months ago by Jani Laakso

  • priority changed from critical to undefined
  • hours_left deleted
  • milestone changed from Testing Tools 1.0 to Product Backlog

Another enhancement here #1485: Testing Tools raport should contain client-side execution "CPU" time for each script line

Changed 10 months ago by Jani Laakso

Merged ticket #1485 here:

User wishes either

  • A. get information (error, notification, whatever) when client-side execution takes longer than X milliseconds.
  • B. see execution time for every test case script line

Used primarily to catch regressions on client-side coding, but can also be used to pinpoint performance issues, e.g. why my build X now consumes 10 seconds when pushing "save" button and for last build it only takes 1 second.

Client-side regressions can be hard to notice and real issues may arise only on more complex setups which RAD does not have time to do testing.

Client-side has this data, it should be passed back to TT.js code and include to test results.

Note: See TracTickets for help on using tickets.