david.calavera - Project Hosting on Google Code

User Profile		Updates

Older Dec 02, 2009 api-11870 r107 (version bump) committed - version bump version bump Dec 02, 2009 api-11870 r106 (solving bugs in cost_get) committed - solving bugs in cost_get solving bugs in cost_get Nov 19, 2009 api-11870 r105 (bumped version) committed - bumped version bumped version Nov 19, 2009 api-11870 r104 (generating the web site with more documentation) committed - generating the web site with more documentation generating the web site with more documentation Nov 19, 2009 api-11870 r103 (refactoring media to avoid write elements as http headers) committed - refactoring media to avoid write elements as http headers refactoring media to avoid write elements as http headers Nov 19, 2009 api-11870 r102 (refactoring site to avoid write elements as http headers) committed - refactoring site to avoid write elements as http headers refactoring site to avoid write elements as http headers Nov 19, 2009 api-11870 r101 (removing eval calls) committed - removing eval calls removing eval calls Nov 19, 2009 api-11870 r100 (refactoring the search class) committed - refactoring the search class refactoring the search class Mar 18, 2009 easyb issue 89 (ability to run one scenario within a story from the command ...) commented on - I think we should implement two methods. The first one is straightforward, adding a command line option called 'scenario' with the description of the scenario that you want to run. i.e: java org.easyb.BehaviorRunner test.story -scenario 'Person object with all properties defined' The second one, adding the story line where the scenario is. i.e: java org.easyb.BehaviorRunner test.story:45 I think we should implement two methods. The first one is straightforward, adding a command line option called 'scenario' with the description of the scenario that you want to run. i.e: java org.easyb.BehaviorRunner test.story -scenario 'Person object with all properties defined' The second one, adding the story line where the scenario is. i.e: java org.easyb.BehaviorRunner test.story:45 Mar 16, 2009 api-11870 r63 (release 0.1.7 ) committed - release 0.1.7 release 0.1.7 Mar 16, 2009 api-11870 r62 (release 0.1.7 ready) committed - release 0.1.7 ready release 0.1.7 ready Mar 16, 2009 api-11870 r61 (user pagination. Thanks to Raul Murciano) committed - user pagination. Thanks to Raul Murciano user pagination. Thanks to Raul Murciano Mar 04, 2009 easyb r646 (shared behaviors some bugs fixed ) committed - shared behaviors some bugs fixed shared behaviors some bugs fixed Feb 28, 2009 easyb r621 (building dependencies and gant tasks updated) committed - building dependencies and gant tasks updated building dependencies and gant tasks updated Feb 25, 2009 easyb issue 134 (After seams not working) Status changed - It seems it's working properly in the development version, I endore my output: java -cp lib/ant-1.6.5.jar:lib/ant-googlecode-0.0.0test.jar:lib/commons-cli-1.1.jar:lib/groovy- 1.5.7.jar:easyb-0.9.4.jar org.disco.easyb.BehaviorRunner test.story -prettyprint Running test story (test.story) 10 11 oooooo Scenarios run: 1, Failures: 0, Pending: 0, Time elapsed: 0.406 sec 1 behavior ran with no failures 1 scenario executed successfully. Story: test scenario before after given test parameters before given test parameters after given test parameters after_each Status: Invalid It seems it's working properly in the development version, I endore my output: java -cp lib/ant-1.6.5.jar:lib/ant-googlecode-0.0.0test.jar:lib/commons-cli-1.1.jar:lib/groovy- 1.5.7.jar:easyb-0.9.4.jar org.disco.easyb.BehaviorRunner test.story -prettyprint Running test story (test.story) 10 11 oooooo Scenarios run: 1, Failures: 0, Pending: 0, Time elapsed: 0.406 sec 1 behavior ran with no failures 1 scenario executed successfully. Story: test scenario before after given test parameters before given test parameters after given test parameters after_each Status: Invalid Feb 24, 2009 easyb issue 117 (ensureThrows list of exceptions) Status changed - Status: Fixed Status: Fixed Feb 24, 2009 easyb r619 (fixes Issue 117: ensureThrows list of exceptions. Now it ...) committed - fixes Issue 117: ensureThrows list of exceptions. Now it support both syntaxes: ensureThrows(RuntimeException) {} ensureThrows([IllegalArgumentException, NullPointerException]) {} Documentation added as well. fixes Issue 117: ensureThrows list of exceptions. Now it support both syntaxes: ensureThrows(RuntimeException) {} ensureThrows([IllegalArgumentException, NullPointerException]) {} Documentation added as well. Feb 24, 2009 easyb r618 (Pretty print option added. It shows the stories and specific...) committed - Pretty print option added. It shows the stories and specifications coloured by the command line if we use the flag -prettyprint. Documentation added for this feature and other undocumented syntax. Pretty print option added. It shows the stories and specifications coloured by the command line if we use the flag -prettyprint. Documentation added for this feature and other undocumented syntax. Feb 03, 2009 easyb issue 110 (add shouldStartWith) Status changed - Status: Fixed Status: Fixed Feb 03, 2009 easyb issue 111 (add shouldEndWith) Status changed - Status: Fixed Status: Fixed Feb 03, 2009 easyb r594 (fixes #110: add shouldStartWith #111: add shouldEndWit...) committed - fixes #110: add shouldStartWith #111: add shouldEndWith fixes #110: add shouldStartWith #111: add shouldEndWith Feb 03, 2009 easyb issue 129 (shouldBeA fails when comparing interfaces) Status changed - Status: Fixed Status: Fixed Feb 03, 2009 easyb r593 (fixes #129: shouldBeA fails when comparing interfaces, thank...) committed - fixes #129: shouldBeA fails when comparing interfaces, thanks to Felipe Rodrigues added a shortcut to ensureThrows ValidationException: i.e: ensureFails { true.shouldBe false } fixes #129: shouldBeA fails when comparing interfaces, thanks to Felipe Rodrigues added a shortcut to ensureThrows ValidationException: i.e: ensureFails { true.shouldBe false } Feb 03, 2009 easyb r592 (target names modified. the "validate-behaviors" task runs ju...) committed - target names modified. the "validate-behaviors" task runs just the behavior tests, the "validate- reports" task runs just the report tests and the "validate" task runs both. By default gant executes the "validate-behaviors" task. target names modified. the "validate-behaviors" task runs just the behavior tests, the "validate- reports" task runs just the report tests and the "validate" task runs both. By default gant executes the "validate-behaviors" task. Feb 02, 2009 easyb issue 126 (Reports don't show specification after fixtures) Status changed - Status: Fixed Status: Fixed Feb 02, 2009 easyb issue 101 (txt reports may miss some children) Status changed - Status: Fixed Status: Fixed Feb 02, 2009 easyb issue 128 ([ENHANCEMENT] Reports refactor) Status changed - Status: Fixed Status: Fixed Feb 02, 2009 easyb r591 (fixes several bugs: #101: txt reports may miss some child...) committed - fixes several bugs: #101: txt reports may miss some children #126: Reports don't show specification after fixtures #128: [ENHANCEMENT] Reports refactor fixes several bugs: #101: txt reports may miss some children #126: Reports don't show specification after fixtures #128: [ENHANCEMENT] Reports refactor Feb 01, 2009 easyb issue 128 ([ENHANCEMENT] Reports refactor) Labels changed - hi, I've found a problem in the previous patch, I've solved it, I endorse a new one Labels: Type-Enhancement −Type-Defect hi, I've found a problem in the previous patch, I've solved it, I endorse a new one Labels: Type-Enhancement −Type-Defect Feb 01, 2009 easyb issue 128 ([ENHANCEMENT] Reports refactor) reported - I've been working on a little refactor of the reports code. Basicaly I wanted to avoid duplicate code, and reorganize and clean the text and html report classes. What I did was: - The behavior steps know how to write themself in the reports. The behavior step type decides the indentation to apply and what's its text representation. - The ResultsCollector knows how to write the results as text. - I've removed logic from the html templates and I've moved it to the html helper. - The TxtStoryReportWriter and the TxtSpecificationReportWriter extend from a common class, TxtReportWriter that groups common code. Finally, if this patch is applied the issue 126 can be closed as well. I've been working on a little refactor of the reports code. Basicaly I wanted to avoid duplicate code, and reorganize and clean the text and html report classes. What I did was: - The behavior steps know how to write themself in the reports. The behavior step type decides the indentation to apply and what's its text representation. - The ResultsCollector knows how to write the results as text. - I've removed logic from the html templates and I've moved it to the html helper. - The TxtStoryReportWriter and the TxtSpecificationReportWriter extend from a common class, TxtReportWriter that groups common code. Finally, if this patch is applied the issue 126 can be closed as well. Jan 30, 2009 easyb issue 126 (Reports don't show specification after fixtures) reported - it was my fault, I forgot to add it, I endorse the patch that solves the problem, sorry it was my fault, I forgot to add it, I endorse the patch that solves the problem, sorry Jan 28, 2009 easyb issue 124 (update build scripts to work with the recent versions of Gan...) reported - Gant version 1.1.1 is obsolete, please update build scripts to use Gant's more recent versions. I endorse a patch that solves this issue. Gant version 1.1.1 is obsolete, please update build scripts to use Gant's more recent versions. I endorse a patch that solves this issue. Jan 28, 2009 easyb issue 103 (add fixtures to .spec) commented on - so, this patch solves that problem XD so, this patch solves that problem XD Jan 25, 2009 easyb issue 103 (add fixtures to .spec) commented on - this issue is fixed, isn't it? the spec WhenStartingBehaviourStep.specification works properly this issue is fixed, isn't it? the spec WhenStartingBehaviourStep.specification works properly Jan 20, 2009 easyb issue 117 (ensureThrows list of exceptions) commented on - I endorse a patch that solves this issue I endorse a patch that solves this issue Jan 20, 2009 easyb issue 110 (add shouldStartWith) commented on - it seems there is an error in the test scenario, but it's just a little mistake int the word "word": then "should end with word", { var.shouldEndWith "word" } should be: then "should end with world", { var.shouldEndWith "world" } it seems there is an error in the test scenario, but it's just a little mistake int the word "word": then "should end with word", { var.shouldEndWith "word" } should be: then "should end with world", { var.shouldEndWith "world" } Jan 19, 2009 easyb issue 111 (add shouldEndWith) commented on - I've submitted a path in the issue #110 that also fixes this one. I've submitted a path in the issue #110 that also fixes this one. Jan 19, 2009 easyb issue 110 (add shouldStartWith) commented on - this path fixes this issue and the next one #111: add shouldEndWith this path fixes this issue and the next one #111: add shouldEndWith Jan 12, 2009 api-11870 r44 (multimedia tests) committed - multimedia tests multimedia tests

issue 128 ([ENHANCEMENT] Reports refactor) reported - I've been working on a little refactor of the reports code. Basicaly I wanted to avoid duplicate code, and reorganize and clean the text and html report classes. What I did was: - The behavior steps know how to write themself in the reports. The behavior step type decides the indentation to apply and what's its text representation. - The ResultsCollector knows how to write the results as text. - I've removed logic from the html templates and I've moved it to the html helper. - The TxtStoryReportWriter and the TxtSpecificationReportWriter extend from a common class, TxtReportWriter that groups common code. Finally, if this patch is applied the issue 126 can be closed as well.

I've been working on a little refactor of the reports code. Basicaly I wanted to avoid duplicate code, and reorganize and clean the text and html report classes. What I did was: - The behavior steps know how to write themself in the reports. The behavior step type decides the indentation to apply and what's its text representation. - The ResultsCollector knows how to write the results as text. - I've removed logic from the html templates and I've moved it to the html helper. - The TxtStoryReportWriter and the TxtSpecificationReportWriter extend from a common class, TxtReportWriter that groups common code. Finally, if this patch is applied the issue 126 can be closed as well.

Older