Service Oriented Architecture Testing

Transcription

1 Internatinal Jurnal f Engineering Research in Cmputer Science and Engineering Vl 5, Issue 4, April 2018 Service Oriented Architecture Testing [1] Mageusha.U, [2] Dr. Sudhamani [1] Research Schlar,Rayalaseema University [2] Research Supervisr, Principal, Vivekananda Degree Cllege fr wmen. Mahalakshmi Layut, Bangalre. Abstract: Service Oriented Architecture is a familiar cncept nwadays. When asked fr definitin f SOA n tw peple wuld end up giving the same answers and mst likely t receive different thughts. Describing SOA as Infrastructure enablers and smene lks SOA as an efficient/ mst effective way f delivering services t Infrmatin Technlgy. Service Oriented Architecture can be defined as A lsely-cupled architecture, which is designed effectively t be reused with the aim f meeting the business need with flexibility and maintainability with an apprach t render the services t the quick t market prjects fr sftware users. Keywrds: SOA, Infrmatin Technlgy, Service Oriented Architecture, Lsely Cupled. INTRODUCTION Service-Oriented Architecture (SOA) it is a strategy fr sftware develpment methds t all the sftware deliverables f an rganizatin, like a basic architectural design f a sftware that represents the varius cmpnents and interactin and accessibility f a sftware. Therefre, service-riented architecture is the creatin f all assets f a sftware rganizatin with strategy - riented methdlgical services. What is Service? Services are features, functins r cmpnents f a prgram, designed and cded t easily interact with ther features f functinalities. these services shuld be simple s that end users f the sftware can be easy t understand, and nt as be a rcket science. Fig 1: Overview f Service. Services can be a granular unit r a piece f cde that delivers/ serves a business need, which can be referred r reused by any ther sftware applicatin t enable the quicker develpment. Services shuld be easy t refer and reuse with minimal cnfiguratin. Services can be cmpared t built-in cmpnents f any sftware and any applicatin can be built n tp f that based n the applicatin requirements. Reusing them frm the applicatin r business prcess as and when need is pssible. Services are defined mre by the business requirements they demand rather than as a flw f data. Service-Oriented Architecture (SOA) is a way f designing, develping, deplying, and managing enterprise systems where business needs and technical slutins are clsely aligned. SOA ffers many ptential benefits, such as cst-efficiency and agility. Hwever, adpting SOA is nt withut cnsiderable challenges. Fr example, the mst cmmn way t implement a SOAbased system is with Web services, but the standards that define Web services are evlving rapidly and many f the Web services tls are still smewhat immature. There is als the questin f hw t leverage existing legacy assets within a SOA cntext. Perhaps mst imprtantly, there are serius challenges related t the testing f SOA-based systems that must be addressed befre the SOA paradigm will enjy brad-based success. All Rights Reserved 2018 IJERCSE 23

2 Internatinal Jurnal f Engineering Research in Cmputer Science and Engineering Vl 5, Issue 4, April 2018 The Evlutin f SOA Service Orientatin (SO) is the natural evlutin f current develpment mdels. First bject-riented mdels; then came the cmpnent-based develpment mdel in the 90s; and nw we have service rientatin mdels (SO). Service rientatin retains the benefits f cmpnent-based develpment (self-descriptin, encapsulatin, dynamic discvery and lading), but there is a shift in paradigm frm remtely invking methds n bjects, t ne f passing messages between services. Schemas describe nt nly the structure f messages, but als behaviral cntracts t define acceptable message exchange patterns and plicies t define service semantics. This prmtes interperability, and thus prvides adaptability benefits, as messages can be sent frm ne service t anther withut cnsideratin f hw the service handling thse messages has been implemented. Fig 2: Evlutin f SOA. Service rientatin has evlved t meet the demand f building lsely cupled distributed sftware that facilitates integratin f existing cmpnents and adaptability. With the emerging f the Web Services, demand fr service rientated architecture has made service-riented sftware develpment pssible with the supprt f develpment tls and wide industry reusability. service rientatin is independent f architectural patterns and technlgy which wuld have access t ld cmpnents. SOA Benefits SOA benefits are basically categrized as fllws: Reducing integratin expense Increasing asset reuse Increasing business agility Reductin f business risk These fur main benefits ffer quicker returns at many parts and hierarchies f the rganizatin, mainly based n the set f business requirements and needs that the cmpany applying the underlying architecture t. SOA being an abstract cncept, understanding its cre principles is essential t succeed. Stries f SOA implementatin failures have been ding runds primarily due t verlking f its fundamental principles f business invlvement and gvernance. The case with SOA testing is n different. The term is even mre ambiguus, and any misinterpretatins can result in failures f test implementatins. The fundatin f SOA testing lies n three basic beliefs - early testing, ptimized cverage and faster regressin. When it vilates ne r mre f these, it is mre likely t fail. Frm my experience, here are sme f the typical situatins where SOA testing des nt give its intended benefits: Late start t get the benefits f SOA it is recmmended that as early as Services are layered in the architecture f cre business functinality. pssibility f Early detectin and fixing f defects prir t integratin f cmpnents is perfrmed t avid cst escalatins due t rewrk. Testing f nn-cre services services that are rarely usable and des nt belng t cre business functinality can be planned in later phases f testing like end t end testing t avid repetitin f testing such cmpnents. All Rights Reserved 2018 IJERCSE 24

3 Internatinal Jurnal f Engineering Research in Cmputer Science and Engineering Vl 5, Issue 4, April 2018 Pr chice f SOA testing tl - Selectin f a SOA testing tl is t be perfrmed mre cnsciusly t meet the demand f business requirements. Ineffective autmatin t avid wastage f autmatin effrts and ensure right cverage f mdules n time, Identifying the right mdules r sftware cmpnents that underg frequent changes can be cnsidered fr autmatin rather than autmating anything and everything Redundant testing cllabratin with test experts n a technical skill shuld g hand in hand t plan the SOA testing in varius test phases t ensure right system testing. Crdinatin and clear Cmmunicatin within businesses SOA based applicatins Testing strategies The nature and effectiveness f Service Oriented Architecture based applicatins calls fr need f defining the test strategies and using f right tlset and test appraches. Older test strategies and appraches might nt be adequate t test the latest SOA based sftware cdes. SOA cnsists f varius technlgies. Applicatins built using SOA has varius services which are lsely cupled. SOA Gvernance SOA Gvernance is abut ensuring that each new and existing service cnfrms t the standards, plicies and bjectives f an rganizatin fr the entire life f that service. Why is SOA Gvernance needed? In tday's challenging business envirnment, SOA Gvernance plays an vital rle in delivering the sftware bjectives by prviding right team structure with needed technical knwledge, business cmmitment and supprt that wuld be prvided during varius phases f sftware develpment life cycle as that f develpment, implementatin and management f SOA. SOA Gvernance prvides the fllwing benefits: Benefits f Business is realized Flexibility in using the Prcess in Business Imprved time t market in a cmpetitive market envirnment Maintenance f services with Quality Ensuring cnsistency f service Test the right sftware deliveries Fig 3: SOA Services SOA Testing shuld fcus n 3 system layers Services layer Includes services expsed by systems which are derived frm business functins. Fr example Service can display the respective data and date being entered. By the user, Services layer cnsists f the services which receives the data frm the Database Lgin Service Prcess layer All Rights Reserved 2018 IJERCSE 25

4 Internatinal Jurnal f Engineering Research in Cmputer Science and Engineering Vl 5, Issue 4, April 2018 Cntain implementatin aspects f business prcesses. let us fcus n prcess mdels which are implemented in user interfaces and prcess layers... The fcus in this layer will be n user interfaces and prcess. Creating, Adding, editing and deleting data Cnsumer layer This layer mainly cmprises f UI based end user interfaces Based n the layer, the testing f an SOA applicatin is distributed int three levels. 1. Service level 2. Interface level 3. End t End level Tp Dwn apprach is used fr Test Designing. Bttm Up apprach is used fr Test Executin. Challenges in Testing SOA-based Applicatins: Planning shuld be dne with utmst care while planning t test SOA based applicatin, failed t d s will result with mre challenges fr testers. Increased test scenaris as and when the sftware reaches the stability Sftware requirement verificatin Identifying the right tl and right capable testers t facilitate smth testing. Multiple stakehlder s invlvement Validatin f accuracy f results Testing dependent cmpnents in a functinal flw. SOA Test Apprach: T break dwn the cmplex sftware slutin int granular, dem able, measurable and manageable piece f cde t build quality deliverables. SOA test apprach shuld fllw the sequence f Cmpnent testing, Service testing, Wrkflw testing, System testing, Integratin testing, Link testing. The fundatins t successful SOA testing are as fllws: a right cmbinatin f Test tls, Technlgy experts and Dmain experienced resurce shuld be deplyed. Test Apprach shuld be designed alng with prject and Technical requirements fr a Prject. Test effrt shuld be estimated and sufficient budget is allcated fr testing. Implement certain measurable metrics thught the lifecycle f the prject. Nnfunctinal tests and security tests shuld be planned frm the initial phase f a Prject. Prper reviews shuld be fllwed during early stages f the prject t ensure that test effrts are planned thrughut the Develpment Life cycle. Test Planning Apprach, Testers shuld understand the cmplete architecture f the applicatin. Break dwn the applicatin int independent services Three cmpnents shuld be rganized Architecture Data/ Back end, Services, and frnt end/ end user applicatins. Right business scenaris are identified and all cmpnents t be cmpletely analyzed. Classificatin between Business scenari and applicatin specific scenari is perfrmed All the business scenaris are tracked thrugh traceability Matrix. All the belw categries f test phases can be fllwed while perfrming SOA testing. Gvernance Testing Service-cmpnent-level testing All Rights Reserved 2018 IJERCSE 26

5 Internatinal Jurnal f Engineering Research in Cmputer Science and Engineering Vl 5, Issue 4, April 2018 Service-level testing Integratin-level testing Prcess/Orchestratin-level testing System-level testing Security Testing Test Executin Apprach Every cmpnent shuld be tested fr right service delivery. Data flws thrugh services as validated thrugh end t end r Integratin testing. Cmplete end t end testing is perfrmed in the system t test bth frnt end, Backend services and their synchrnizatin. Perfrmance testing and Respnse time testing shuld be dne with varius data lads fr ptimum perfrmance. SOA Architecture Testing apprach We shuld understand, hw t break dwn the architecture t its cmpnent parts, wrking frm the very basic t the mst cmplex cmpnents, testing each cmpnent, then the integratin f the cmplete architecture. Test autmatin framewrk fr SOA: Devising autmatin slutin fr SOA starts with feasibility study and tl analysis fr suitability fr SOA. It is necessary t design test scenaris that fcus n individual transactins as well as business wrkflws s that issues, if any, can be identified and islated. Sme ppular SOA test tls available t test include: sapui Pr, HP Service Test, Parasft's SOAtest t name a few. In sme cases, web services r ther cmpnents may nt have an interface hence a UI may need t be develped t test them. Nn-UI based testing is als quite a cmmn scenari. CONCLUSION The study f Service riented architecture helps the testers t understand the sftware architecture f enterprise including pririties, practices and cncepts f applicatin side, varius services and its repsitry. Service riented architecture is a cllectin f layers, and each layer has a unique functinality, the first layer (Services Layer) Includes services expsed by systems which are derived frm business functins, and this layer delivers an apprpriate business that prvides lgic and test data which is necessary fr varius phases f testing applicatin. The secnd layer (Prcess Layer) can address varius user interfaces and prcess. Finally, the third layer, (Cnsumer Layer) This layer mainly cmprises f user interfaces. SOA will prvide the supprt fr the business prcess / Services / prcess f the rganizatin and ensure that right selectin, understanding and utilizing f test tls blended with crrect technlgy starting frm early phase f the prject results in quality deliverable with fixes dne in early phases that results in cst reductin invlved in maintenance f a prject and quicker t Markets.. REFERENCES: 1) Mathur, AP (2008) Fundatins f sftware testing. Drling, Kindersley (India), Pearsn Educatin in Suth Asia, Delhi, India. 2) Y, S, Harman M (2012) Regressin testing minimizatin, selectin and priritizatin: A survey. Sftw Test Verif Reliab 22(2): Fig 4: Test autmatin framewrk 3) B. Beizer, Sftware Testing Techniques, Secnd Editin. Published by dreamtech, New Delhi, pp , 2008 All Rights Reserved 2018 IJERCSE 27

6 Internatinal Jurnal f Engineering Research in Cmputer Science and Engineering Vl 5, Issue 4, April ) Z. Li, M. Harman, and R. M. Hierns, Search algrithms fr regressin test case priritizatin, IEEE Transactins n Sftware Engineering, vl.33, n. 4. 5) Testing Strategies and Tactics fr Mbile Applicatins [Online]. Available: All Rights Reserved 2018 IJERCSE 28