openerp-expert-framework team mailing list archive

[Nhomar Hernández <nhomar@xxxxxxxxx>]

Only One thing we want to add.

We have a lot of procedures to proof concepts on openERP, and Ferdinand is
right.
@fabien.

Is very very important to make a simple howto and conceptual manual to
develop this test cases, because, in the documentation some times the
concepts for several thing and functions are missing.
In other words, put in the manual not only the steps, but, put the reasons
of the tests examples and make complex examples, we can invest a lot on ti
cases, because is very useful to deploy in the future.

If is possible put it on the OpenERP SA's plans, related to the write all
tests scenarios.

Thanks

2010/2/24 Fabien Pinckaers <fp@xxxxxxxxxxx>

> I totally agree. I have a meeting with our CTO today to discuss how we
> can change our internal development methodology to be Behaviour Driven
> Development. It means that for every development and bugfix, we plan to:
>  * first write a test scenario
>  * then implement the solution
> We will start this in trunk, for the next version.
>
> I would suggest all contributors/partners to do the same when they do
> merge proposals or bugfixes.
>
> Thanks,
>
> Ferdinand Gassauer wrote:
> > Just want to emphasize the need for an "expert testing tool".
> >
> > This tool will make it possible to
> > a) create test cases for request of customers
> > b) formalize the test environment.
> > c) show test to customer - because he can read input and output
> >
> > I consider this as a crucial step which is absolutely necessary to
> "protect"
> > partners and Tiny.
> > Till now I'd say OpenERP is a product for "very friendly customers".
> >
> > I am not talking so much about the technical quality and concept which
> IMHO is
> > not the only issue here.
> > The problem is the complexity of an ERP System, especially one with that
> many
> > modules. So everyone extending the system must and with OpenERP Scenario
>  will
> > have the chance to verify that the functionality is not violated.
> >
> > Given what we have seen during the life cycle of 5.0, which was/is
> considered
> > as "stable", I just have to say that at least I was running into major
> > functional problems (especially accounting issues) - which have been
> widely
> > not considered as bugs by Tiny - every other week, because of
> > a) missing features - I do not blame anyone for this, it's part of the
> game to
> > enhance OpenERP, but we must have a chance to do so.
> > b) incomplete coding - things work only in certain cases (Example: random
> > numbering of invoices having multiple journals with same code)
> > c) coding errors - functional wrong behavior (Example: reuse of same
> sequence
> > for statement and line)
> > d) wrong functional implementations (Example: evaluation of past stock
> > quantity with current avg price)
> >
> > So I think we all will profit from test cases because it will be easy -
> > especially for new partners - to see what is tested and what perhaps not.
> >
>
>
> --
> Fabien Pinckaers
> CEO Tiny - OpenERP Editor
> Chaussée de Namur 40
> B-1367 Grand-Rosière
> Belgium
> Phone: +32.81.81.37.00
> Fax: +32.81.73.35.01
> Web: http://openerp.com
>
> Great Achievements Start With Tiny Investments
>  -- Marty, 2005
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-expert-framework<https://launchpad.net/%7Eopenerp-expert-framework>
> Post to     : openerp-expert-framework@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-expert-framework<https://launchpad.net/%7Eopenerp-expert-framework>
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Saludos Cordiales

Nhomar G. Hernandez M.
+58-414-4110269
+58-212-6615932
+58-212-9536734 ext 124
+58-212-9512643
Web-Blog: http://geronimo.com.ve
Servicios IT: http://openerp.netquatro.com
Linux-Counter: 467724
Correos:
nhomar.hernandez@xxxxxxxxxxxxx
nhomar@xxxxxxxxxxxxxxx