In BizTalk Application Testing Life Cycle -3 – Integration Testing
In BizTalk Application Testing Life Cycle -1 – we have
tested the Application Functionality on the basis of Function requirement
agreed with the business.
For Details Please Check:http://geekswithblogs.net/AbhishekLohani/archive/2012/09/19/biztalk-application-testing-life-cycle-part-1.aspxv
In BizTalk Application Testing Life Cycle -2 – we have
tested the Application Functionality on the basis of Non Function requirement
agreed with the business.
For Details Please Check:http://geekswithblogs.net/AbhishekLohani/archive/2013/01/22/biztalk-application-testing-life-cycle-part-2.aspxhttp://geekswithblogs.net/AbhishekLohani/archive/2013/01/22/biztalk-application-testing-life-cycle-part-2.aspx
In BizTalk Application Testing Life Cycle -3 – we need to
tested how the Application/ System wiil interacting with Third Party software / Custom Software / Legacy sytem as per agreed with business
Issue faced in Integration Testing
·
Might be the Input file schema changes during
the development of system and valid file discarded by system
·
May be New Version / New release of Custom or
Third Party Software is release during
new system development.
·
Requirement was fixed wrongly with assumption if
this type of file will come following action will took place but not act when
actual file came.
·
New Software support the legacy system to give
the result end to end.
In BizTalk Application Testing Life Cycle -3 – Integration Testing
In BizTalk Application Testing Life Cycle -1 – we have
tested the Application Functionality on the basis of Function requirement
agreed with the business.
For Details Please Check:
In BizTalk Application Testing Life Cycle -2 – we have
tested the Application Functionality on the basis of Non Function requirement
agreed with the business.
For Details Please Check:
In BizTalk Application Testing Life Cycle -3 – we need to
tested the Application with interacting with Third Party software
Issue faced in Integration Testing
·
Might be the Input file schema changes during
the development of system and valid file discarded by system
·
May be New Version / New release of Custom or
Third Party Software is release during
new system development.
·
Requirement was fixed wrongly with assumption if
this type of file will come following action will took place but not act when
actual file came.
·
New Software support the legacy system to give
the result end to end.
Thanks & Regards
Abhishek