zierp-developer — Development and design information

[Zierp-developer] functional requirements

[Stins, D. www.Zion-IT.c. <DR...@Zi...>]

ThaniX,

I like your ideas.

The web erp manual is valid. The current software is an unchanged fork of
web-erp 2.9b except for the theme and some bug fixes.

Can you and Patrick work this out until we are able to create a planning for
writing functional requirements with the goal to enable excellent testing?

With best regards,

Dick Stins

----- Original Message ----- 
From: "Breeze Undefined" <bre...@gm...>
To: <eng...@ea...>
Cc: "Stins, Dick www.Zion-IT.com" <DR...@zi...>; "Doomster"
<ele...@ne...>; "thanix" <th...@us...>
Sent: Sunday, June 19, 2005 5:45 PM
Subject: Re: recurring stuff specification


On 6/19/05, eng...@ea... <eng...@ea...> wrote:
> The problem we have is we do not know the correct functionality of the
> system as it isn't documented on the functionality, so accordingly how are
> we to write test scripts without the knowledge to evaluate what is right
or
> wrong.
> I am uncomfortable just flying into this with our eyes closed on testing
> when I have no clue as to the way it should work.
>
>
        So, let us create the documentation first. "functionality of
the system" as said above,  I presume, is with respect to the "ERP
knowledge".  Is it not?   If it is so, let us look at the already
available ERP software around and get it from them, I examined a few
"ERP5.org" is one and major of them. Unfortunately, the "all about
ERP" manual was in french, some of you might be able to use it.

         Part one, would be the documentation/system plan  given by
the developers of the system. Part two, for all testing purposes, we
require domain knowledge and the requirements that the project is
supposed to meet (that would be requirements specification by the
users). Is there a requirements document available?

       If Part two documentation is not available, we would require
part one. What I wanted to know is:  "Is the webERP manual sufficient
for this purpose?"  or should we require tailoring it to the zierp?

       To get a clue on how things are supposed to work, do we need to
find a roundabout way?  Download some of the available ERP software
and start using it. May be we can, then proceed further. :)

Thanks & Regards,
ThaniX

[Zierp-developer] testing, functional requirements documentation

[Stins, D. www.Zion-IT.c. <DR...@Zi...>]

Patrick,

Thanks for your reply.

I agree that we need functional requirements to enable excellent testing.

That is exactly one of the reasons why I started this project. Lack of
documentation.

Fortunately, it is not that bad. We got something and that is more then
nothing.

We got the manual at the wackowiki.
http://wacko.zion-it.com/ZionITERPDevelopmentTeam

We got the on-line help.

And the other stuff at the wackowiki.

We got the sources.

We got the testenvironment.

Fortunately are a lot of the scripts just basic insert update delete scripts
enhanced with foreign key checks and/or buttons for printing, calling other
simple scripts, ...
Foreign keys are implemented to secure data integrity.

This give me the feeling that we are able to test 80% of Zion-IT-ERP with
the current documentation set.

The kind of functional requirements were you are looking for does not exist.
Please tell me or setup a template (at the wackowiki or ....) for anything
you need for proper testing.
This could be used to write the required documentation for proper testing.
I prefer to get this documentation finished as soon as possible.
Also the phpdoc documentation in the source code (see developers lists
message) is one of the steps for the documentation.

I requested Artegonio to create the datamodel documentation and improve the
datamodel.

In the meanwhile current testing which can be done is based at the current
information available.
One goal is to get rid of all displayed errors and warnings which are native
sql and/or php errors or showed in the error_log file.
Functional errors can only detected when you and/or the other testers
recognise unrealistic functional behaviour of the application. With your ERP
expertise, I think that you are of great value to detect these functional
errors.
To document what is tested, to know how much time it takes to redo it again,
we need to have testplans/cases/......
Hopefully we are able to enhence those testplans/cases soon with
requirements in the functional documentation.

It would be great when you (or another volunteer, but you sounds like you
exactly know wat you need for proper testing) setups a template for the
required functional documentation and create a system/planning to monitor
this.
I prefer not to add new functionality (like hrms) until this firm basis is
finished.

When you need help, then please inform me/us/.... I always can try to
recruit other documentalists or may be someone in the team (like me) would
like to work at it.

I hope that the testers are able start with the moduletest and will produce
input for the functional requirements documentation.
It is obvious that they can't test the functional requirements properly,
because we do not have them yet....

With best regards,

Dick Stins

----- Original Message ----- 
From: <eng...@ea...>
To: "Stins, Dick www.Zion-IT.com" <DR...@Zi...>; "Breeze Undefined"
<bre...@gm...>
Cc: "Doomster" <ele...@ne...>
Sent: Sunday, June 19, 2005 4:27 PM
Subject: Re: recurring stuff specification


> The problem we have is we do not know the correct functionality of the
> system as it isn't documented on the functionality, so accordingly how are
> we to write test scripts without the knowledge to evaluate what is right
or
> wrong.
> I am uncomfortable just flying into this with our eyes closed on testing
> when I have no clue as to the way it should work.
>
> > [Original Message]
> > From: Stins, Dick www.Zion-IT.com <DR...@Zi...>
> > To: Breeze Undefined <bre...@gm...>
> > Cc: Doomster <ele...@ne...>; <eng...@ea...>
> > John mentioned an idea for using automatic testing tools, but with or
> > without automatic testing tools, we still need to define what to test.
> >
> > From technical perspective, we change script files. When we release a
new
> > script file, then we need to have a testplan for this script.
> >
> > I call this a module test.
> >
> > My suggestion is that you start to setup per module:
> > - test plan
> >   * description test cases
> >   * ....
> > - test sets
> > - test results
> > - .....
> >
> > It would be nice to be able to reuse the testsets or have scripts to
> > recreate them.
> >
> > I think that it would be nice to describe it all at the wackowiki, but
any
> > other suggestion is welcome too.
> > The advantage at the wackowiki is that you can mark (put your name
behind
> > the script....) the scripts where you are working at and it is accesible
> to
> > the others.
> >
> > I setup a page
> > (http://wacko.zion-it.com/ZionITERPDevelopmentTeam/TestModules )  with
> > all(?) scripts (please tidy up this page to your prefered method). When
> you
> > doubleclick (or click at edit), you can enter your name behind the
script
> to
> > indicate you are working at this moduletest.
> > When you hit the question mark, you create a new page for the specific
> > moduletest.
> >
> > Another option to coordinate/manage the testing is too create issues at
> our
> > support tool. The issues can then be assigned. When they/you consider
> that,
> > then I prefer to put all test issues/tasks at a separate project. I
> already
> > create a subproject moduletest. You can move to this at
> > http://zierptest.zion-it.com/support by selecting it in the right upper
> > corner (button Switch).
> >
> > Feel free to contact Patrick and John (  mailto:eng...@ea...
> > ,  ele...@ne...
> >  ) and also to contact me when you need help or have any other question.
> >
> > With best regards,
> >
> > Dick Stins
> >
> > ----- Original Message ----- 
> > From: "Breeze Undefined" <bre...@gm...>
> > To: "Stins, Dick www.Zion-IT.com" <DR...@zi...>
> > Sent: Sunday, June 19, 2005 7:52 AM
> > Subject: Re: recurring stuff specification
> >
> >
> > Dear Stins, Dick
> >
> >           I explored the http://zierptest.zion-it.com/   and have gone
> > through the "webERP manual".
> >
> >           I couldn't go about "sales order" as I do not have the
> > customer details. I have only the login (user: gast), and I cannot
> > really get into testing. I would want you to assist me regarding this.
> > I would like to take up a particular "task", so that I am clear in
> > whatever I take up and complete it.
> >
> >           Can you please give me the contact details of my test
> > co-ordinators. I shall ask them guidance on this.  Please do contact
> > me, if you want to clarify with me.
> >
> > Anticipating your reply,
> > Thanks,
> > ThaniX
> >

[Zierp-developer] Hi I am ThaniX (from the testing team)

[Breeze U. <bre...@gm...>]

Dear all,
=20
        This is my first mail to this developer's list. So, would take
this opportunity to introduce to the team. I am ThaniX  - I am in the=20
"testing team" of this project.

        I have subscribed to this 'developer list' and at the 'issue
tracker(zmantis)'.
=20
        I had a visit to the WackoSite
(http://wacko.zion-it.com/ZionITERP). There is just the links to the
test site and the support.  Where is the files section?  The online
manual is a good thing in place, I am reading it and parallely
exploring the test site.

        Hoping for communication from John/Patrick.=20

Thanks & regards,
ThaniX

[Zierp-developer] datamodelling ERD (re-)assignment

[Stins, D. www.Zion-IT.c. <DR...@Zi...>]

BlankUnfortunately had Sam to reassign, because he has no time cause by
unxpected events.

Claudio is the new candidate for this position.

Claudio please contact me by sending me your e-mail address.

My e-mail was bounced by sourceforge instead of forwarded to you.

with best regards,

Dick Stins

[Zierp-developer] test tool http://sourceforge.net/projects/webinject/

[Stins, D. www.Zion-IT.c. <DR...@Zi...>]

Blanktest tool:

 http://sourceforge.net/projects/webinject/

Is this test tool usable?

with best regards,

Dick Stins

[Zierp-developer] results/progress/status/todo

[Stins, D. www.Zion-IT.c. <DR...@Zi...>]

BlankResults:
- for contributors is a demo available for testing, documentation
- ddl script will be send on request to contributors
- mantis bugtracker is setup for evaluation
- some project standards:
1. lines in scripts=80 characters
2. indent of 2 is standard for php scripts
3. use of classes is recommended in php
4. wrappers are not welcome (there might be some exceptions allowed.... )
5. new releases will only be released as stable when the test team is
finished with testing and it is released as pre-release candidate during 4
weeks without reported major bugs.
6. the php scripts should be properly documented with phpdocumentor (javadoc
style)before they are planned to test.
7. ....

Current activities are:
- setup professional test traject (Patrick? John?)
- reverse engineer datamodel + redesign (Sam)
- research for database layer code generator (Dick Stins + Blue Gard? + ..?)

I will do:
* setup wacko wiki
* setup demo (not for testing)

Who would like to start with:
 - information analysis
   * reverse engineer functional requirements
   * business rules
 - documentation
   * technical (PHPDOCUMENTOR)
   * user manual
    * tutorial
 - write a code generator for the database layer (please ask for
information)
 - redesign the error and message handling (may be integrated/generated in
database layer)
 - setup/maintain a good looking project website with the content management
system phpwebsite
- .....

With best regards,

Dick Stins