Hi Expert,
I met one scenario that customer want to combine two scripts which are based on different systems into one composite test script. For example, I create one sales order on ECC system and then I hand over the order number to another system like CRM.
What I currently find out that if I want to use composite test for this, I need firstly to create two composite tests and each composite contains one script. Then I need to use a third composite test to combine the two composites together and thus I can run the two scripts on different systems. So I'm wondering if there's easy way to use one composite and contains different scripts based on different systems? These systems may not be in one logical component. Thanks.
Best Regards,
Nick
4 Answers
-
Best Answer
Former MemberApr 19, 2017 at 07:23 AMHi Nick.
Yes this approach is possible. You can simply create separate test configurations for each SUT and prepare input and output parameters. After that composite test can be created. Add those test configurations in and link your parameters together. Simple as that.
Each SUT needs to be properly connected via managed system configuration, than special configuration for CBTA is needed (TST_<SID>CLNT<CLNT> RFC, User, parameters and so on) and then SDC updated and test profiles set up. Then if each script is working then it is OK to add them in composite test.
I personally created few of these composite tests where information were transferred from customer's web applications to CRM and then to ERP.
Hope it helps.
Bye.
Add comment
-
Jan 31, 2017 at 06:54 AM
Hi Nick
Not sure and I haven't tried this but an idea could be to start on first system and then use a RFC destination on that first system (again not sure this is supported) to jump to the second system. Worth a try I would think.
Best regards
Tom
Add comment
-
Former MemberFeb 09, 2017 at 04:25 PM
Hi Nick,
I am also in the same phase, i am trying to run CRM test script first and then to run ECC script. I did follow the same step that you have mentioned. But i am wondering after CBTA_GUI_A_LAUNCHANDLOGIN step, how did you handle to run next steps, Did you plug in the recorded script or or did you record the script or did you put the components manually into test script.
Should be appreciated.
Thank you
Add comment
-
Former MemberFeb 15, 2017 at 11:19 PM
I believe this is the right approach. I did this a year ago so I am a little fuzzy on the details.
I went into SOLAR_PROJECT_ADMIN and opened the project that has the test cases your are creating. In the System Landscape tab I added the logical component so now all SIDs in your test scenario are in your project's landscape. Then in the Business Blueprint I manually added the structure and transactions for the new landscape.
I edited the System Data Container (SDC) to include the new target system with the additional logical component. In SUT Management I synchronized the SDC so the new logical component shows up in the hierarchy. I was then able to add the connection (RFC and user accounts) for the new landscape.
After all this I can create a new CBTA test case and point to the SUTs under either logical component and use the appropriate test profile to log in. You can also create one composite that calls all scripts in your E2E scenario. Hopefully this makes sense at a high level and somebody else can correct or validate what I described.
Add comment
Add comment