
Hi all, Have done some investigations on Perl testing frameworks, and it seems like it is not so difficult to accomplish a test framework for otrs. Anyone else familiar with eXtreme Programming here? Is anyone interested in developing a test framework for future versions of otrs like otrs v3.0? Greger

Hi Greger, bobsmith1@marketweighton.com wrote:
Have done some investigations on Perl testing frameworks, and it seems like it is not so difficult to accomplish a test framework for otrs.
Anyone else familiar with eXtreme Programming here?
Is anyone interested in developing a test framework for future versions of otrs like otrs v3.0?
Yes. .-) We already discussed this issue. -=> I see to different points for a testing framework. a) test of core modules (Kernel/System/*.pm) b) test of the web interface (Kernel/Modules/*.pm) I would say, "a" is the easier one. "b" not (if we don't want to switch to an extra XML layer for the gui (performance issue)). Has somebody experience with testing frameworks for web applications?
Greger
Martin Edenhofer -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!

On 26 Mar, Martin Edenhofer wrote:
We already discussed this issue. -=> I see to different points for a testing framework.
a) test of core modules (Kernel/System/*.pm)
b) test of the web interface (Kernel/Modules/*.pm)
I would say, "a" is the easier one. "b" not (if we don't want to switch to an extra XML layer for the gui (performance issue)).
Has somebody experience with testing frameworks for web applications?
Yes. HTTP::WebTest::Test, Test::TempDatabase, Test::MockDBI, nebst anderen.

Hi Steven, Steven Schubiger wrote:
We already discussed this issue. -=> I see to different points for a testing framework.
a) test of core modules (Kernel/System/*.pm)
b) test of the web interface (Kernel/Modules/*.pm)
I would say, "a" is the easier one. "b" not (if we don't want to switch to an extra XML layer for the gui (performance issue)).
Has somebody experience with testing frameworks for web applications?
Yes.
HTTP::WebTest::Test, Test::TempDatabase, Test::MockDBI, nebst anderen.
Fine! :) I have a question about HTTP::WebTest and the wt script. What is the normal procedure to record a new test scenario (write each http request by your self in the wt script or is there a more comfortable way)? Thanks! Martin Edenhofer -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!

On 26 Mar, Martin Edenhofer wrote:
I have a question about HTTP::WebTest and the wt script.
What is the normal procedure to record a new test scenario (write each http request by your self in the wt script or is there a more comfortable way)?
I'd say, divert all power directly to HTTP::WebTest's methods, since all wt does, is invoking the HTTP::WebTest's new && run_wtscript methods.
participants (3)
-
bobsmith1@marketweighton.com
-
Martin Edenhofer
-
Steven Schubiger