![]() Similarly Mail Box: Check its integration to the Delete Mails Module. Here do not concentrate much on the Login Page testing as it’s already been done in Unit Testing. But check how it’s linked to the Mail Box Page. Sample Integration Test Cases for the following scenario: Application has 3 modules say ‘Login Page’, ‘Mailbox’ and ‘Delete emails’ and each of them is integrated logically. Here priority is to be given for the integrating links rather than the unit functions which are already tested. Integration Test Case differs from other test cases in the sense it focuses mainly on the interfaces & flow of data/information between the modules. Inadequate exception handling could cause issues.Ĭlick here if the video is not accessible.External Hardware interfaces, if any, could be erroneous.Interfaces of the software modules with the database could be erroneous. ![]() These new requirements may not be unit tested and hence system integration Testing becomes necessary. ![]() At the time of module development, there are wide chances of change in requirements by the clients.Integration Testing becomes necessary to verify the software modules work in unity A Module, in general, is designed by an individual software developer whose understanding and programming logic may differ from other programmers.Although each software module is unit tested, defects still exist for various reasons like ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |