Workflow development enviroment, any tips

Next topic

Author	Message
Tore Skobba	Thursday 16 December 2004 6:28:01 am Hi I am working on an workflow for the first time. And I find the testing of it very inefficient.. I.e my workflow works on registred users and I have to register an user each time I have to test it. Just wondering if anybody have set up an test enviroment or something for workflow development and have some tips to share. Cheers Tore
Xavier Dutoit	Thursday 16 December 2004 10:43:46 am My first tip is to avoid coffee when working on a workflow, that's taf enough without ;) More seriously, that's a pain, be prepared. I've worked on an event triggered post publication, the only few tips I could find to smooth the process where to alter the event, so that's easier to rerun (eg. instead of running the event upon the creation of the object, runs it when you upgrade it). This way, instead of having to create the object (the user ?) each time, you "only" have to modify one. Don't know if it's useful in your case. Also, install a php optimiser (I've found mmtruck faster than php accelerator), so the time you spoil waiting on the computer is (slightly) shorter. The ez crew is well aware of the problem, and told us it won't be addressed on the 3.6 rel. See this post: http://ez.no/community/forum/suggestions/call_for_comments_focus_on_web_developer_usability_issues_in_ez_publish_3_6 Good luck. Xavier http://www.sydesy.com

Author

Message

Thursday 16 December 2004 6:28:01 am

I am working on an workflow for the first time. And I find the testing of it very inefficient.. I.e my workflow works on registred users and I have to register an user each time I have to test it. Just wondering if anybody have set up an test enviroment or something for workflow development and have some tips to share.

Cheers
Tore

Xavier Dutoit

Thursday 16 December 2004 10:43:46 am

My first tip is to avoid coffee when working on a workflow, that's taf enough without ;)

More seriously, that's a pain, be prepared. I've worked on an event triggered post publication, the only few tips I could find to smooth the process where to alter the event, so that's easier to rerun (eg. instead of running the event upon the creation of the object, runs it when you upgrade it). This way, instead of having to create the object (the user ?) each time, you "only" have to modify one. Don't know if it's useful in your case. Also, install a php optimiser (I've found mmtruck faster than php accelerator), so the time you spoil waiting on the computer is (slightly) shorter.

The ez crew is well aware of the problem, and told us it won't be addressed on the 3.6 rel. See this post: http://ez.no/community/forum/suggestions/call_for_comments_focus_on_web_developer_usability_issues_in_ez_publish_3_6

Good luck.

Xavier

http://www.sydesy.com

eZ debug

Timing:	Jan 18 2025 18:17:29
Script start
Timing:	Jan 18 2025 18:17:29
Module start 'layout'
Timing:	Jan 18 2025 18:17:29
Module start 'content'
Timing:	Jan 18 2025 18:17:31
Module end 'content'
Timing:	Jan 18 2025 18:17:31
Script end

Main resources:

Total runtime	1.8698 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0050	589.1797	152.6406
Module start 'layout'	0.0050	0.0030	741.8203	39.4766
Module start 'content'	0.0080	1.8603	781.2969	521.0781
Module end 'content'	1.8683	0.0014	1,302.3750	8.2813
Script end	1.8697		1,310.6563

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.1775	16	0.0002
Check MTime	0.0014	0.0750	16	0.0001
Mysql Total
Database connection	0.0006	0.0331	1	0.0006
Mysqli_queries	1.4839	79.3651	54	0.0275
Looping result	0.0006	0.0312	52	0.0000
Template Total	1.4971	80.1	2	0.7485
Template load	0.0021	0.1130	2	0.0011
Template processing	1.4950	79.9549	2	0.7475
Template load and register function	0.0001	0.0079	1	0.0001
states
state_id_array	0.0022	0.1164	1	0.0022
state_identifier_array	0.0025	0.1334	2	0.0012
Override
Cache load	0.0018	0.0952	14	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0009	0.0496	2	0.0005
Fetch class attribute name	0.0020	0.1064	3	0.0007
XML
Image XML parsing	0.0009	0.0462	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0009	3	0.0000
General
dbfile	0.0016	0.0865	16	0.0001
String conversion	0.0000	0.0003	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 9 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs