*** Aiste has joined #zope3-dev | 00:05 | |
*** Aiste has quit IRC | 00:26 | |
*** bradb has quit IRC | 00:41 | |
*** niemeyer has quit IRC | 01:13 | |
*** SureshZ has left #zope3-dev | 01:21 | |
*** elbixio has quit IRC | 01:26 | |
*** yota has quit IRC | 01:31 | |
*** tarek has quit IRC | 01:35 | |
*** srichter has quit IRC | 01:37 | |
*** hazmat_ has quit IRC | 01:39 | |
*** dagnachew has quit IRC | 01:40 | |
*** bskahan has joined #zope3-dev | 02:59 | |
*** srichter has joined #zope3-dev | 03:08 | |
*** bskahan has quit IRC | 03:16 | |
*** __odie has joined #zope3-dev | 04:26 | |
*** projekt01 has quit IRC | 04:38 | |
*** __odie has quit IRC | 04:46 | |
*** stub has joined #zope3-dev | 04:58 | |
*** elbixio has joined #zope3-dev | 05:19 | |
*** bradb has joined #zope3-dev | 05:23 | |
*** elbixio has quit IRC | 05:56 | |
*** elbixio has joined #zope3-dev | 08:15 | |
*** elbixio has quit IRC | 08:18 | |
*** guido_g has quit IRC | 08:23 | |
*** timte has joined #zope3-dev | 08:25 | |
*** tvon has quit IRC | 08:49 | |
*** tvon has joined #zope3-dev | 08:53 | |
*** hdima has joined #zope3-dev | 09:13 | |
*** zagy__ is now known as zagy | 09:18 | |
*** guido_g has joined #zope3-dev | 09:19 | |
*** yota has joined #zope3-dev | 09:27 | |
*** mooded has joined #zope3-dev | 09:31 | |
*** Theuni has joined #zope3-dev | 09:38 | |
*** tarek has joined #zope3-dev | 09:57 | |
*** sashav has joined #zope3-dev | 10:00 | |
*** __gotcha_ has quit IRC | 10:16 | |
*** gintas has joined #zope3-dev | 10:21 | |
*** mexiKON has joined #zope3-dev | 10:41 | |
*** philiKON has quit IRC | 10:49 | |
*** lunatik has joined #zope3-dev | 10:56 | |
*** lunatik has left #zope3-dev | 10:59 | |
*** vinsci is now known as vinsci|2 | 11:05 | |
*** faassen has joined #zope3-dev | 11:18 | |
*** ChrisW has joined #zope3-dev | 12:13 | |
ChrisW | anyone here? | 12:13 |
---|---|---|
VladDrac | plenty | 12:16 |
*** ChrisW has left #zope3-dev | 12:16 | |
*** Aiste has joined #zope3-dev | 12:20 | |
*** gintas has quit IRC | 12:31 | |
*** projekt01 has joined #zope3-dev | 12:47 | |
*** vlado has joined #zope3-dev | 13:03 | |
*** jhauser has joined #zope3-dev | 13:06 | |
*** Aiste has quit IRC | 13:15 | |
*** andrew_m has joined #zope3-dev | 13:26 | |
*** bskahan has joined #zope3-dev | 13:35 | |
*** dagnachew has joined #zope3-dev | 13:42 | |
*** dagnachew has quit IRC | 13:57 | |
*** srichter has quit IRC | 13:58 | |
*** timte has quit IRC | 14:01 | |
*** Aiste has joined #zope3-dev | 14:22 | |
*** srichter has joined #zope3-dev | 14:52 | |
*** ChanServ sets mode: +o srichter | 14:52 | |
*** dagnachew has joined #zope3-dev | 15:04 | |
*** ignas has joined #zope3-dev | 15:28 | |
*** regebro has joined #zope3-dev | 15:35 | |
*** alga has joined #zope3-dev | 15:42 | |
*** dagnachew has quit IRC | 15:53 | |
*** niemeyer has joined #zope3-dev | 16:08 | |
*** sashav has quit IRC | 16:18 | |
*** guido_g has quit IRC | 16:35 | |
*** lunatik has joined #zope3-dev | 16:36 | |
*** BjornT has joined #zope3-dev | 16:38 | |
*** lunatik has left #zope3-dev | 16:49 | |
*** alga has quit IRC | 16:52 | |
*** zagy has quit IRC | 16:52 | |
*** SureshZ has joined #zope3-dev | 16:58 | |
*** stub has quit IRC | 17:17 | |
*** tarek has quit IRC | 17:19 | |
*** tarek has joined #zope3-dev | 17:20 | |
*** tarek has joined #zope3-dev | 17:23 | |
*** hdima has quit IRC | 17:38 | |
*** alga has joined #zope3-dev | 18:00 | |
*** mooded has quit IRC | 18:22 | |
*** Aiste has quit IRC | 18:45 | |
*** elbixio has joined #zope3-dev | 18:59 | |
*** Theuni has quit IRC | 19:07 | |
*** elbixio has quit IRC | 19:26 | |
*** regebro has quit IRC | 19:34 | |
*** faassen has quit IRC | 19:44 | |
bradb | i'm trying to register a custom display widget. in my browser:schemadisplay directive, i've got: | 19:52 |
bradb | <browser:widget | 19:52 |
bradb | field="bugdescription" | 19:52 |
bradb | class="canonical.launchpad.browser.widgets.BugDescriptionDisplayWidget" /> | 19:52 |
bradb | when trying to start my z3 instance though, i get: | 19:52 |
bradb | ConfigurationError: ('Invalid directive', u'widget') | 19:52 |
bradb | i expected it to not raise an exception. why did it raise an exception instead of simply registering my custom display widget like i asked? | 19:53 |
mexiKON | no browser: namesapce | 19:55 |
mexiKON | simply use <widget ... /> | 19:55 |
bradb | ouch | 19:55 |
bradb | so, for edit forms you use browser: but /not/ for schemadisplays? :) | 19:55 |
mexiKON | huh? | 19:56 |
mexiKON | <browser:editform ...><widget ... /></browser:editform> | 19:56 |
mexiKON | tyhat's what i always use | 19:57 |
mexiKON | same with addform | 19:57 |
bradb | i use browser:widget | 19:57 |
mexiKON | oh | 19:57 |
mexiKON | hmm | 19:57 |
mexiKON | i c now, you want schemadisplay | 19:57 |
mexiKON | does schemadisplay even support the widget subdirective? | 19:57 |
bradb | it's documented that it does, yes | 19:57 |
mexiKON | hmm, it does, indeed | 19:57 |
mexiKON | weird | 19:57 |
mexiKON | bradb, will you be at EP? | 19:58 |
bradb | not this year, unfortunately. :) too much work to do + moving into a new place right now. | 19:59 |
*** elbixio has joined #zope3-dev | 19:59 | |
mexiKON | ic | 20:00 |
mexiKON | too bad | 20:00 |
elbixio | hi, are pluggableauth and pau related or do they provide completly different functionality? | 20:03 |
mexiKON | pluggableauth is x3.0 | 20:04 |
mexiKON | pau is 3.1 | 20:04 |
mexiKON | those numbers are zope versions in case you're wondering | 20:04 |
elbixio | :O | 20:04 |
mexiKON | so, yes, they provide the same functionaity | 20:04 |
mexiKON | pluggableauth will be deprecated with zope 3.1 | 20:05 |
elbixio | but if i try to use Zope trunk i could use pau | 20:05 |
mexiKON | yep | 20:08 |
mexiKON | you really should | 20:08 |
elbixio | ok, i'll read the apidoc, thanks philipp | 20:08 |
mexiKON | np | 20:10 |
*** J1m has joined #zope3-dev | 20:13 | |
*** __odie has joined #zope3-dev | 20:13 | |
*** dagnachew has joined #zope3-dev | 20:15 | |
mexiKON | hi J1m | 20:16 |
mexiKON | do you have a minute? i would like to talk to you about a testing issue i have | 20:16 |
J1m | k | 20:18 |
J1m | mexiKON, what's up? | 20:19 |
*** bradb is now known as bradb|lunch | 20:21 | |
mexiKON | J1m, so | 20:21 |
mexiKON | J1m, it's about Five | 20:21 |
mexiKON | Five has >70 tests now | 20:21 |
mexiKON | we used to do testing like this: there was a "FiveTest" product that had all the mock objects; tests would play around with those | 20:22 |
mexiKON | of course, this makes tests neither atomic nor is it easy to refactor. it's also harder and harder to add more tests because "FiveTest" grew | 20:22 |
mexiKON | so got rid of FiveTest | 20:22 |
mexiKON | problem is this: | 20:22 |
J1m | 70? | 20:22 |
mexiKON | yup | 20:23 |
mexiKON | more than 70 | 20:23 |
J1m | That's not very many | 20:23 |
mexiKON | it isn't | 20:23 |
mexiKON | but the number will increase | 20:23 |
mexiKON | i hope | 20:23 |
mexiKON | that's my goal at least | 20:23 |
J1m | So what is wrong with unit tests? | 20:23 |
mexiKON | so i want to make sure we do it right | 20:23 |
mexiKON | problem is this: | 20:23 |
mexiKON | it's hard to not make a unit test an integration test in Zope 2 | 20:24 |
mexiKON | that's just the way tests are in Zope 2 | 20:24 |
mexiKON | or, rather, ZopeTestCase-based tests | 20:24 |
mexiKON | so, most tests rely on Five's ZCML being executed | 20:25 |
mexiKON | because they need the services, etc. etc. | 20:25 |
J1m | I'm not sure I believe that. I was able to make unit tests for ZClasses. | 20:25 |
J1m | well, that's not entirely true | 20:25 |
J1m | anyway, go ahead with your question. | 20:25 |
mexiKON | we have *some* unit tests | 20:25 |
mexiKON | but very few | 20:26 |
mexiKON | if you want test stuff like Five-based traversal, it's hard to test w/o the object actually in the whole Zope 2 context | 20:26 |
mexiKON | so, most tests need Five ZCML being executed, also becaus ethey themselves would like to execute some ZCML so they want the metadirectives to be active | 20:27 |
mexiKON | of course, by loading custom ZCML, each test case also loads stuff | 20:27 |
mexiKON | we want this to be cleaned up | 20:27 |
mexiKON | cleanup after every test and reexecuting Five's ZCML + some custom ZCML is very very very slow | 20:27 |
mexiKON | i thought of doing setUp/tearDown before adn after every test *suite* | 20:28 |
J1m | You should look at the layer support in my new test runner | 20:28 |
mexiKON | but, alas, the test runner grabs the individual test cases and puts them into itsown suite | 20:28 |
mexiKON | layer support... hmm. how does that work and help me? | 20:28 |
J1m | (My new test runner is being used for ZODB 3.4, and will be used for Zope 2.9 and 3.2) | 20:28 |
mexiKON | cool | 20:28 |
J1m | Look at the documentation first. :) | 20:29 |
mexiKON | note that this is Zope 2.7 in the wrost case | 20:29 |
mexiKON | ok | 20:29 |
mexiKON | are you sure that the zope 2.7 test runner has this? | 20:29 |
J1m | http://svn.zope.org/zope.testing/trunk/src/zope/testing/testrunner.txt?rev=30503&view=markup | 20:29 |
J1m | No, Zope 2.7 doesn't have this. | 20:30 |
J1m | Now does Zope 2.8 or 3.1 | 20:30 |
J1m | Nor does Zope 2.8 or 3.1 | 20:30 |
J1m | Is Five limited to the Zope 2.7 test runner? | 20:30 |
mexiKON | well, we need a Zope 2.7 solution | 20:30 |
mexiKON | well, Five is at least included in Zope 2.8, so we're limited to what Zope 2.8 has | 20:31 |
J1m | I wonder if that is strictly necessary | 20:31 |
mexiKON | you want to be able to run all the tests in a Zope 2.8 release with its rest runner, right? | 20:31 |
J1m | It would be nice | 20:31 |
J1m | alternatively you could use the same trick the Z3 functional tests currently use. | 20:32 |
*** __odie has quit IRC | 20:32 | |
mexiKON | what's that? | 20:32 |
J1m | They have a separate setup thing that they run once. | 20:32 |
J1m | It's a bit of a hack | 20:32 |
J1m | But the set up runs the first time a functional test runs | 20:32 |
J1m | That may not work for you though | 20:33 |
mexiKON | well, that's what sorta have now | 20:33 |
mexiKON | i want tesets to be more atomic, though | 20:33 |
J1m | Z3 knows to run the functional tests after the unit tests. | 20:33 |
J1m | I thought you wanted to share setup? | 20:33 |
mexiKON | between the tests of one test suite | 20:33 |
mexiKON | yes | 20:33 |
mexiKON | take a doctest, for example | 20:33 |
mexiKON | lots of tests, one setUp/tearDown | 20:33 |
mexiKON | (I want to convert more stuff to doctests, too) | 20:34 |
J1m | Another problem is that ZCML doesn't provide any facilities for tearing down. | 20:34 |
J1m | It might be nice if it did. | 20:34 |
mexiKON | well, what i do is this: | 20:34 |
mexiKON | i load zcml, but don't execute actions | 20:35 |
mexiKON | no, wait, i used to do that | 20:35 |
mexiKON | never mind | 20:35 |
mexiKON | what i do is: | 20:35 |
mexiKON | to setUp, i load the zcml | 20:35 |
mexiKON | to tearDown, i use placelesssetup.tearDown | 20:35 |
mexiKON | all the services gone -> all zcml is gone | 20:35 |
J1m | some z3 zcml modified module globals. | 20:36 |
J1m | some z3 zcml modifies module globals. | 20:36 |
mexiKON | yes, and some <five: /> directives monkey patch classes | 20:36 |
mexiKON | but that's a minor glitch | 20:36 |
mexiKON | a glitch that even Zope 3 doesnt' cope with | 20:36 |
mexiKON | unless you have explicit tearDown | 20:36 |
*** elbixio has quit IRC | 20:36 | |
J1m | It does in the case of functional tests by running them last. | 20:37 |
mexiKON | true | 20:37 |
J1m | do you have a question? :) | 20:38 |
mexiKON | i'm pondering | 20:38 |
mexiKON | it's not obvious for me what to do | 20:38 |
mexiKON | i guess i should a) convert as much to doctests | 20:38 |
mexiKON | and b) try to minimize the amount of config needed for a test case so that individual and atomic setup/teardown isn't so expensive | 20:39 |
J1m | You could probably design a test suite that has it's own suite-based setUp and tearDown. | 20:39 |
mexiKON | i did that already | 20:39 |
mexiKON | it works when running each test module individually | 20:39 |
mexiKON | python2.3 tests/test_foobar.py | 20:39 |
mexiKON | however, the zope test runner ignores the custom test suite, it uses a bulk one and inserts the tests into that | 20:40 |
J1m | I guess that's true. So does mine, now that you mention it. | 20:42 |
J1m | I don't have any ideas for you off the top of my head. | 20:43 |
J1m | And I need to get back to thinking about multi-database zope 3 apps :) | 20:43 |
mexiKON | ok :) | 20:49 |
*** __odie has joined #zope3-dev | 20:52 | |
*** srichter has quit IRC | 21:02 | |
*** dagnachew has quit IRC | 21:06 | |
*** bradb|lunch is now known as bradb | 21:09 | |
*** bskahan has quit IRC | 21:21 | |
*** mgedmin has joined #zope3-dev | 21:32 | |
*** srichter has joined #zope3-dev | 21:32 | |
*** ChanServ sets mode: +o srichter | 21:33 | |
*** __gotcha_ has joined #zope3-dev | 21:59 | |
*** __gotcha_ is now known as __gotcha | 21:59 | |
*** dagnachew has joined #zope3-dev | 22:18 | |
*** mgedmin has quit IRC | 22:28 | |
projekt01 | Hi together, I'll working on the nested menu implementation for the Boston skin right now. | 22:28 |
projekt01 | Does anybody has a better idea then using the javasript "IE7" for build nested dropdown menus | 22:29 |
projekt01 | Otherwise I will implement it like here: | 22:30 |
projekt01 | D:\prototype\menu\version_2\index.html | 22:30 |
projekt01 | Ok, that was the wrong copy/paste | 22:30 |
projekt01 | http://www.kundenprojekt.ch/demo/index.html | 22:30 |
*** ignas has quit IRC | 23:01 | |
*** __odie has quit IRC | 23:11 | |
*** __odie has joined #zope3-dev | 23:12 | |
*** alga has quit IRC | 23:21 | |
*** __odie has quit IRC | 23:22 | |
*** _projekt01 has joined #zope3-dev | 23:37 | |
*** bradb is now known as bradb|afk | 23:39 | |
*** projekt01 has quit IRC | 23:39 | |
*** nederhoed has joined #zope3-dev | 23:53 | |
nederhoed | hello? | 23:54 |
*** nederhoed has left #zope3-dev | 23:57 | |
*** nederhoed_ has joined #zope3-dev | 23:59 |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!