Re: NonUnicode to Unicode testing

To: arslist@ARSLIST.ORG Subject: Re: NonUnicode to Unicode testing ** Hello All, Thanks a lot for the response. The migration will be performed by some other team, we need to test whether migration is sucessfull or not. For this I have created some test cases for testing using remedy client

NonUnicode to Unicode testing

Hello All, We have to test the nonunicode to uncode migration of Remedy ARS 7.6. Please sahre the possible scenarios that should be considered. or Some special cases that needs to be tested both from client and web. OS: windows Database:Oracle Remedy ARS 7.6 regards Sahil

Re: NonUnicode to Unicode testing

Hi, 1. Use the API to transfer both DATA and your Application (DEF-files). 2. When transering data through the API, it is good to make set Client Charset to UTF-8, otherwise your data might get corrupted. I have typically used RRR|Chive to do this. Just add a parameter in the rrrchive config

Re: NonUnicode to Unicode testing

Hello All, Thanks a lot for the response. The migration will be performed by some other team, we need to test whether migration is sucessfull or not. For this I have created some test cases for testing using remedy client and web, So I would request few of those scenarios (only test scenarios)

Re: NonUnicode to Unicode testing

Hi, Both Mid-Tier and ARUser.exe are complient, and need not be tested as such. You have to verify the DATA and DEF though. 1. Review old tickets containing multi-byte characters in the data 2. Submit/retrieve new multi-byte data 3. If field labels, messages etc in the system contain multi-byte

Re: NonUnicode to Unicode testing

To: arslist@ARSLIST.ORG Subject: Re: NonUnicode to Unicode testing ** Hello All, Thanks a lot for the response. The migration will be performed by some other team, we need to test whether migration is sucessfull or not. For this I have created some test cases for testing using remedy client and web