Please use this identifier to cite or link to this item: http://10.1.7.192:80/jspui/handle/123456789/8772
Full metadata record
DC FieldValueLanguage
dc.contributor.authorShukla, Shruti Sanjaykumar-
dc.date.accessioned2019-08-21T09:43:59Z-
dc.date.available2019-08-21T09:43:59Z-
dc.date.issued2017-06-01-
dc.identifier.urihttp://10.1.7.192:80/jspui/handle/123456789/8772-
dc.description.abstractEIT (Enterprise Integration Testing) Automation Testing comes under the unified field of Software Testing in Computer Science. Automation Testing is to help the testers to complete their tasks and so that the quality of product can be assured. The real customers of Automation Team is Manual Testers. All the framework ,requirements are uploaded on OTM (Online Testing Manual) from where the automation testers gets their queue of work. Automation Testers creates and develops scripts and test the products in their environment. After which these automated scripts are run in manual tester’s environment. Automation Testing has again two parts: Smoke and Functional Scenarios. Smoke Scenarios can be seen as Integration testing context of Software Testing and while Functional Scenarios is Unit testing context in Software Testing in Computer Science.Open Script and Synergy , two internal tools of oracle are used to develop automated test cases. out of all products of Oracle, mainly this project includes Retail Merchandising System (RMS), Storage Inventory Management (SIM), Warehouse Management System (RWMS) and others including Retail Integration Bus (RIB). Second part of project includes, replacing of controller tables with spreadsheet and we need to automate ”Foundation Data”.As products of Oracle were moving to cloud, Automation on cloud without controller tables encouraged the use of Spreadsheet and this then implied to built new functional libraries and test cases for Foundation Data. In conclusion, we know that automation test is limited to a boundaries, that is not all test cases can be automated still here we are trying to automate as much test cases as we can in order to provide more stable and less cost testing scenarios to help the manual testers.en_US
dc.publisherInstitute of Technologyen_US
dc.relation.ispartofseries15MCEC26;-
dc.subjectComputer 2015en_US
dc.subjectProject Report 2015en_US
dc.subjectComputer Project Reporten_US
dc.subjectProject Reporten_US
dc.subject15MCEen_US
dc.subject15MCECen_US
dc.subject15MCEC26en_US
dc.titleEIT Automation and Testingen_US
dc.typeDissertationen_US
Appears in Collections:Dissertation, CE

Files in This Item:
File Description SizeFormat 
15MCEC26.pdf15MCEC266.43 MBAdobe PDFThumbnail
View/Open


Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.