Introduction 2 Data driven method 2.1 Data state within the integration layer 2.

2 Data state within the database layer 2.3 Data state within the Application layer 3 See also Introduction SIT is part of the software testing life cycle for collaborative projects. Usual ly, a round of SIT precedes the user acceptance test (UAT) round. And software p roviders usually run a pre-SIT round before consumers run their SIT test cases. For example, if integrator (company) is providing an enhancement to customer's e xisting solution, then they integrate the new application layer and the new data base layer with existing customer's application and existing database layers. Af ter the integration completes, users use the new part (extended part) of the int egrated application to update data. Along they use old part (pre-existing part) of the integrated application. A process should exist to exchange data imports a nd exports between the two data layers. This data exchange process should keep b oth systems up-to-date. Purpose of the system integration testing is to make sur e whether these systems are successfully integrated and been up-to-date by excha nging data with each other. There may be more parties in the integration, for example the customer (consumer ) can have their own customers; there may be also multiple providers. Data driven method This article contains instructions, advice, or how-to content. The purpo se of Wikipedia is to present facts, not to train. Please help improve this arti cle either by rewriting the how-to content or by moving it to Wikiversity or Wik ibooks. (November 2011) This is a simple method which can perform with minimum usage of the software tes ting tools. Exchange some data imports and data exports. And then investigate th e behavior of each data field within each individual layer. There are three main states of data flow after the software collaboration has done. Data state within the integration layer Integration layer can be a middleware or web service(s) which is act as a media for data imports and data exports. Perform some data imports and exports and che ck following steps. 1. Cross check the data properties within the Integration layer with technical/b usiness specification documents. - If web service involved with the integration layer then we can use WSDL and XS D against our web service request for the cross check. - If middleware involved with the integration layer then we can use data mapping s against middleware logs for the cross check. 2. Execute some unit tests. Cross check the data mappings (data positions, decla rations) and requests (character length, data types) with technical specificatio ns. 3. Investigate the server logs/middleware logs for troubleshooting. (Reading knowledge of WSDL, XSD, DTD, XML, and EDI might be required for this)

Data state within the database layer 1. First check whether all the data have committed to the database layer from th e integration layer. 2. Then check the data properties with the table and column properties with rele vant to technical/business specification documents. 3. Check the data validations/constrains with business specification documents. 4. If there are any processing data within the database layer then check Stored Procedures with relevant specifications. 5. Investigate the server logs for troubleshooting. (Knowledge in SQL and reading knowledge in stored procedures might be required f or this) Data state within the Application layer There is not that much to do with the application layer when we perform a system integration testing. 1. Mark all the fields from business requirement documents which should be visib le in the UI. 2. Create a data map from database fields to application fields and check whethe r necessary fields are visible in UI. 3. Check data properties by some positive and negative test cases. There are many combinations of data imports and export which we can perform by c onsidering the time period for system integration testing (We have to select best combinations to perform with the limited time). And also we have to repeat some of the above steps in order to test those combinations