Javis Toggle Final 3
Bloomingbit Newsroom
공유하기
Summary
- It was pointed out that the process related to Javis Toggle is complex, and it was stated that there is a need to check the entire undelivered and resend.
- It was clarified that even if the toggle is not in a normal state, it is necessary to confirm the possibility that sharing can occur twice.
- It was emphasized that Hankyung sharing is an exception that is not included in the test scope.
- Check entire undelivered > modify > resend
Undelivered status > Toggle is in hold
- Check entire delivery > modify > toggle hold
Whether normal or not, X sharing requires checking if the toggle ON\\<->OFF is causing actual double sharing
- Register reservation > modify > check toggle status (does not apply if scenario is in hold)
- Exception: Hankyung sharing is excluded from the test scope
