Sprint #3 Testing Tools - Unblocking 1.0

[Joonas Lehtinen]

Check included slides to actual content

[Joonas Lehtinen]

Jouni

[Joonas Lehtinen]

Jouni, please review. Are XML import / export still blockers?

[Jani Laakso]

Jouni check from the customer but..

Why capsulate structural data again another format as XML? We already got the data in structural format in SQL database which is nice to query and update. external XML interface will get complex: using another data format and storing place would imply that we need to resolve synchronization conflicts when someone changes database and another guy tries to import same object through XML import interface.

• solution 1: use POJO's through our clean API
  • our API uses JDBC under the hood
• solution 2: simplest would be to use plain JDBC
  • on JDBC we have LOCK and RELEASE methods to use to prevent "conflicts"
• idea: keep database the only authoritative place for all data

See #1366

[Jani Laakso]

About versioning.

We already got some kind of versioning. Test case has only one instance of (latest) test case script, but when any test case is executed then test case script is copied to test case result. Hence even if you change test case later, test results still contain old / original version of the script which was used at the time when test case was executed.

Is this enough for E?

[Jani Laakso]

About JSP sivujen testaus

We should explore what possibilities XPCOM and "users.js" brings out for testing multiple IFRAME's. There might be elegant solutions available as security issues are no longer an obstacle. We can for example inject javascript without Toolkit application using custom FF session and communicate between IFRAME's freely.

[Jani Laakso]

Jouni, WHat about regression testing, does E need it? If so, then few enhancements and bugfixes are required aswell for this sprint.