Versions Compared

Old Version 21

changes.mady.by.user Jakub Sławiński

Saved on

compared with

New Version 22

changes.mady.by.user Jakub Sławiński

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Helper class

Description

CollectionSheetEntryTestHelper

Contains methods to:

  • navigate to CSE page
  • fill the form
  • submit

BatchJobHelper

Contains methods to run all/some batch jobs.

OfficeHelper
(there are currently two such classes)

Contains methods to:

  • create new offices
  • verify offices list
  • change office ststus
  • enter/verify QG related to offices

SavingsAccountHelper

Contains methods to:

  • create new savings accounts
  • navigate to various savings pages
  • add notes
  • make deposits/withdrawals
  • handle QG related to savings
  • close/activate/change status
  • verify due values

HolidayTestHelper

Contains methods to create new holidays.

CustomPropertiesHelper

 

AdminTestHelper

 

CenterTestHelper

 

FormParametersHelper

  Contains methods to set various Mifos properties
(you can find properties' descriptions at this page)

AdminTestHelper

Contains methods to:

  • navigate to/define/verify lookups options
  • navigate to/define/verify labels
  • navigate to/define/edit checklists
  • navigate to System Info page

CenterTestHelper

Contains methods to:

  • create new centers
  • navigate to view center details page
  • change status
  • apply charge

FormParametersHelper

Contains methods to create form parameters for:

  • loan products
  • client personal data
  • fees

ReportTestHelper

 

ClientTestHelper

 

UserHelper

 

NavigationHelper

 

QuestionGroupTestHelper

 

GroupTestHelper

 

LoanTestHelper

 

SavingsProductHelper

 

FeeTestHelper

 

FeesHelper

 

LoanProductTestHelper

 

...

DB unit dependency

As part of MIFOS-4590   4590     , there is currently an on-going effort to refactor the current suite of acceptance tests to minimize dependency on the DB unit based XML datasets. As a result, a new test group, no_db_unit, has been introduced to categorize tests that do not need DB unit dependency. Currently, the Maven POM for acceptance tests, ensures that all tests in the no_db_unit group are executed prior to executing the rest of the acceptance tests. This ensures that the no_db_unit group of tests do not inadvertently depend on the XML data sets used by the older tests.

...