Charm:Status To be tested

[Former Member]

Hello all,

Short clarification regarding behavior of normal changes in status To be tested. In case there is 3 tier scenario landscape and we have a normal change (call it NC 123) which is in status to be tested (means ToC is already in QAS), the maint cycle gets switched to TEST phase so this normal change wont be possible to be set to Successfully tested status. When there is an integration test being performed it means that this integration test is happening in such a case in other "release version" because in QAS we are already testing release including NC123 (it was imported to QAS with ToC already), but to PROD NC123 will not be imported during golive as NC123 was not set to Successfully tested before phase switch of maint cycle to TEST. Is that correct? How this can be overcome?

Thanks a lot for your help.

[former_member229755]

Hi Julius,

We have a 4 tier landscape and we do face this issue at times. This risk has to be considered by both Functional & Testing Team during Integration Test Planning phase. All Inter-dependencies across the modules will have to considered prior to approving the requirement. This can be achieved by doing a Cross impact analysis.

We have a Regression Test suite which is executed in the pre-prod environment for each release to ensure core functionalities are not affected. This is to ensure any defects that have been slipped through the integration phase be caught during the Regression Test Suite, we can also automate this Regression Test Suite using an Automation Tool like UFT etc.

I hope this helps.

Regards,

Prasath

[Former Member]

Thanks a lot Prasath for sharing your hints! I appreciate that.

[Former Member]

Hello Miguel,

thanks a lot for your feedback. So my understanding was correct if I get it right from your answer. Yes sequence break and downgrade risk etc. is another topic to take care of. I was just analyzing various situations which can happen and this issue with NC copied to QaS via ToC, but not released for production yet and thus kind of jeopardizing integration testing on QaS grabed my attention. I wanted to assure i understand the process correctly.

From what I know 4 tier landscape design with integration testing being performed on 3rd tier would solve this issue.

[Miguel_Ariño]

So, NC 123 is in status To be tested.

When you import a Maintenance Cycle into production, the NC 123 will show up during the completion activities. You still have a chance then to go back and import the transport requests for NC 123 on QAS and PRD if needed.

Maybe what you mean is: what happens if NC 124 and 125 are imported into PRD before 123. Perhaps you need to set up Downgrade Protection, if your question is that what happens if other changes overtake NC123.

https://wiki.scn.sap.com/wiki/display/SM/How+to+work+with+Change+Request+Management+Downgrade+Protec...

[Former Member]

Hi Prasath,

I know why the NC 123 will not be imported to prod, reason you've described is known to me. It's not the real situation we are facing, its more theoretical topic. NC123 will not be marked as successfully tested due to any reason e.g. test will not be done due to lack of time or something else. In maintenance cycles this can happen.This NC will then be overtaken to next maintenance cycle. However the situation I described above will still happen in current maint cycle and integration scenario will be tested in QAS already with NC123 while it will be in PROD without NC123. I hope you guys can understand what I mean.

Thank you

[Former Member]

Hi Julius,

In this case NC123 will can not be imported to Prod for one more reason, the Original Transport is not yet released. Also, could you please let us know the reason for Switching the MNT Cycle phase to Test before releasing the Original Transport and marking the change in "Successfully Tested" status?

Regards,

Prasath