Testing the Partner Edit Screen's Address Functionality

From OpenPetra Wiki
Revision as of 15:01, 18 March 2016 by Christiankatict (talk | contribs) (→‎Known Bugs!)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Overview

There a many, many ways in how addresses can be handled in the Partner Edit screen. This list gives an idea on how to enter and test many of those scenarios.

A reference on the details of advanced Address Tab functionality can be found here; this information should be used whenever the steps below are performed!

Creation of New Partners

Creation of new Partners of all Partner Classes, with a focus on PERSONs.

  • With no address.
  • With one or more addresses in either of the following ways:
    • completely new addresses entered manually;
    • manual entering of an existing address and…
      • accepting the ‘similar address’ that OpenPetra found;
      • not accepting the ‘similar address’ that OpenPetra found;
    • finding of an address...
      • replacing an existing address of the Partner;
      • when a new, empty address has just been created;
    • Deletion of one or more addresses.

Important:

  • ... with all of those operations: saving of data in at various in-between stages, or only at the end.
  • ... with all of those operations: create new Partners from the Main Menu, with the 'New Partner' functionality of the Partner Edit screen (ToolBarButton or File Menu MenuItem by that name) or by clicking the 'Create new Person for this Family' Button on the 'Family Members' Tab (only available when current Partner is of Partner Class FAMILY).

Opening of existing Partners of all Partner Classes (it doesn’t matter where a Partner gets opened from in Petra)

... and working with Addresses in all of the ways described above:

  • Opening of Partners that have no address on file;
  • Opening of Partners that have one or more addresses on file;
  • Adding / changing of one or more addresses in the following ways:
    • completely new addresses entered manually;
    • manual entering of an existing address and...
      • accepting the ‘similar address’ that OpenPetra found;
      • not accepting the ‘similar address’ that OpenPetra found;
    • finding of an address...
      • replacing an existing address of the Partner;
      • when a new, empty address has just been created;
  • Changing of one or more addresses of a Partner that other Partners have got, too (address change promotion dialog!).
  • Various FAMILY -> PERSON ‘promotion features’:
    • See various sections of the above mentioned wiki page!
  • Deletion of one or more addresses.

Important:

  • ...with all of those operations: saving of data in at various in-between stages, or only at the end.

Assessing Test Results

  • It is important to not only check that the performed operations yielded no obvious error (e.g. Exception occurring, Address Tab not showing what it ought to) but to open a Partner after a save operation has taken place to assess whether all changes have taken place as they ought to!
    • If other Partners ought to have been affected by a particular operation then those need to be opened as well to assess that what ought to have happened has indeed happened!
  • It can be helpful to have the Partner Find screen open in parallel as it gets refreshed whenever a Partner gets changed, and so will display Address changes, too. This is also a neat place from which to re-open a Partner (see bullet point above).

Simulating Real User Behaviour

With all of the listed operations it would be good (time permitting) to not only specifically perform 'Address related' data entry / data changes but in addition also a few other changes, e.g. at the top of the Partner Edit screen or on other Tabs of the Partner Edit screen, to 'simulate ordinary work' that users would do day-in, day-out on the Partner Edit screen.

Known Bugs!

This list is current as of March 3rd, 2016 and specifically contains Bugs that directly relate to specific functionality of the Address Tab, such as functionality mentioned here:

Fixed in the meantime!