Here is what I think we need to do for integration testing.
| Table of Contents |
|---|
EAS address will not show up in AVS without an address parcel link.
1.0) Data Combinations and Permutations
...
1.1) Create a base address with no AXPparcel link.
pass
2.1) Add AXP parcel to existing base address.
pass
3.1) Create a unit address with no AXPparcel.
pass
4.1) Add the AXP parcel to the unit address
4.1.1) unit: "100"
4.1.2) unit: "100 2A"
4.1.3) unit: "A"
4.1.4) unit: "A 100 A"
pass
5.1) Create address with 1/2 (100 1/2 Main)
pass
5.2) Create address with lots of AXPsparcels
pass
5.3) Retired address with lots of parcels
pass
6.1) Retire lots of AXPs from address but keep unit address
7.1) Create address with 1/2 (100 1/2 Main) pass
2.0) Big Data
...
2.1) Retire address with lots of data.
i.e. 2655 hyde
pass
2.2) Create address with lots of data.
i.e. 2655 hyde
pass
3.0) Order
...
To some degree we rely on the order of change notification.
But we do not guarantee order within a single change request.
There we need to test the following scenarios.
3.1) within a single CRchange request, retire 100 main, then create 100 main
3.2) within a single CRchange request, create 100 main, then retire 100 main
Passes but with this issue http://code.google.com/p/eas/issues/detail?id=442
4.0) Combination
...
4.1) Retire - Create
4.2) Create many base-unit-axp in a single change request.
already done
5.0) Business Cases
...
5.1) Process street parcel retirement Review
pass
5.2) Process parcel street retirement
5.3) Lot split (do we have the data, can we find the data?)
5.4) lot merge (do we have the data, can we find the data?)Review
pass