> I think bug qualification and assignation policies should be deeply
> reviewed...
I think we need more tests (YAML) for the stock module:
- if your industry needs the QC flow, with incoming, controlled, quarrantine
and rejected locations, we need a series of tests to prove all this sequence
of steps.
- on the other hand, we will also need corresponding tests for the simple
cases (no production lot, simple "shelf" locations) to ensure that smaller
businesses will still be able to operate.
Please, community, help us formulate your requirements in terms of tests, so
that each release of OpenERP will be proven to follow your procedures.
I imagine a set of tests like (expressed in YAML format) :
-
I will test the suitability of stock for automotive/pharmaceutical industry
# Considering ISO 9000, FDA-xxxx, IEC-xxxx, LP Bug 722538 ...
# <More comments about the nature of requirements, with references to
# specifications and known practices >
-
By specification, I have to create stock locations for incoming lots, to-be-
reviewed items, ....
-
!record {model: stock.location}:
....
-
I receive a batch of items
-
...and so on
In 1 year time, few people may remember that bug 722538 in some proprietary
site had information about these procedures. But if our own "code" contains
solid references to the needed results, we are more likely to follow (and not
break) them in the long run.
On Sunday 06 March 2011, you wrote:
> I think bug qualification and assignation policies should be deeply
> reviewed...
I think we need more tests (YAML) for the stock module:
- if your industry needs the QC flow, with incoming, controlled, quarrantine
and rejected locations, we need a series of tests to prove all this sequence
of steps.
- on the other hand, we will also need corresponding tests for the simple
cases (no production lot, simple "shelf" locations) to ensure that smaller
businesses will still be able to operate.
Please, community, help us formulate your requirements in terms of tests, so
that each release of OpenERP will be proven to follow your procedures.
I imagine a set of tests like (expressed in YAML format) :
- pharmaceutical industry
I will test the suitability of stock for automotive/
# Considering ISO 9000, FDA-xxxx, IEC-xxxx, LP Bug 722538 ...
# <More comments about the nature of requirements, with references to
# specifications and known practices >
-
By specification, I have to create stock locations for incoming lots, to-be-
reviewed items, ....
-
!record {model: stock.location}:
....
-
I receive a batch of items
-
...and so on
In 1 year time, few people may remember that bug 722538 in some proprietary
site had information about these procedures. But if our own "code" contains
solid references to the needed results, we are more likely to follow (and not
break) them in the long run.