SOAP & SOAPUI

The main groups of Testing are Functional and Non-Functional..Security Testing could be at this general level as if not part of a specification. If Security Testing is addressed in a specification, it would be deemed part of the functional tests.

Functional Testing

1. bases test cases on the specifications of the software component under test
2. The identification of functions that the software is expected to perform
3. The creation of input data based on the function's specifications
4. The determination of output based on the function's specifications
5. The execution of the test case
6. The comparison of actual and expected outputs

This should simplify your approach to Agile management. The concept is to stay in the center 'sweet spot'. Gravitating into one state of mind has an equal effect on the Agile balance. Staying in the zone, means the client gets what they need, its built well, and project cost is competitive.

For example: Too much energy on doing the Right Thing(massive feature set?, causes time to market to suffer and it may not be done correctly so updates and maintenance could be a night mare.

Groovy Script in SOAPUI allow for reaching out to external data and return reporting elements and data

• Open Flie/DB connection
• Read from Excel/Database
• Re-Name Test Steps from Excel Columns
• Get Values from spreadsheet/database for test step(s) values
• Use variables/properties for
  • logging
  • Renaming Test Cases on-the-fly
  • Populating Request Messages
  • Populating Response Messages
  • Resetting Test Case to default values
• Closing Flies/DB connections

Script Logging

log.info( "NEXT: : " + curTC.getPropertyValue("Symbol") ) 
log.info( "Test Case TearDown.." )

TestSuite

SetupScript

log.info(runner.getTestSuite().toString())
log.info(runner.toString())