#61 Server-con-1601 The scenario leads test to fail
To test if server sends status 424 (size mismatch),
the SyncML Tool should send to each database the
first chunk with the command <MoreData/> and expect
to receive the status 213, then the second chunk and
expect to receive status 424.
The first bug is related to the variables
FirstChunkSend and LastChunkSend: just after the
SyncML tool send the last chunk and set
FirstChunkSend to 0 (@ line 688), it tests if the
FirstChunkSend is equal to 0 (@ line 692), set it to
1 and set LastChunkSend to 0. Next time it will send
the last chunk without sending the first chunk. i.e.:
(calendar: firstChunk + <MoreData>, then lastChunk),
(vcard: lastChunk).
The second bug is related to part that test the Add’s
status values, there’s only one test (@ line 567) to
check if the status value is equal to 213. When the
server receives the first chunk with the command
<MoreData/> it will replay with status 213, but when
it receive the second chunk and the size is invalid
it will replay with status 424. Witch lead the test
to fail.
Logged In: YES
user_id=1357631
Fix reprot:
Purpose:
This patch is to fix Bug 1370291 for SCTS DS1.1.2
Description of the Patch
The variables FirstChunkSend and LastChunkSend are not
correctly initialized:
After setting FirstChunkSend to 0 (@ line 688), it tests
if this variable is equal to 0 (@ line 692), set it to 1
and set LastChunkSend to 0. Next time it will send the
last chunk without sending the first chunk.
And the status 424, for invalid size, is never checked.
Short overview of how the patch works
Add variable SwitchFirstLastChunk to do a correct switch.
If the variable FirstChunkSend is equal to 1 (first chunk
was sent), test if the status is 213,
else if variable LastChunkSend is equal to 1 (last chunk
was sent), test if the status is 424.
Logged In: YES
user_id=1357631
Fix reprot:
Purpose:
This patch is to fix Bug 1370291 for SCTS DS1.1.2
Description of the Patch
The variables FirstChunkSend and LastChunkSend are not
correctly initialized:
After setting FirstChunkSend to 0 (@ line 688), it tests
if this variable is equal to 0 (@ line 692), set it to 1
and set LastChunkSend to 0. Next time it will send the
last chunk without sending the first chunk.
And the status 424, for invalid size, is never checked.
Short overview of how the patch works
Add variable SwitchFirstLastChunk to do a correct switch.
If the variable FirstChunkSend is equal to 1 (first chunk
was sent), test if the status is 213,
else if variable LastChunkSend is equal to 1 (last chunk
was sent), test if the status is 424.
Logged In: YES
user_id=1357631
Fix reprot:
Purpose:
This patch is to fix Bug 1370291 for SCTS DS1.1.2
Description of the Patch
The variables FirstChunkSend and LastChunkSend are not
correctly initialized:
After setting FirstChunkSend to 0 (@ line 688), it tests
if this variable is equal to 0 (@ line 692), set it to 1
and set LastChunkSend to 0. Next time it will send the
last chunk without sending the first chunk.
And the status 424, for invalid size, is never checked.
Short overview of how the patch works
Add variable SwitchFirstLastChunk to do a correct switch.
If the variable FirstChunkSend is equal to 1 (first chunk
was sent), test if the status is 213,
else if variable LastChunkSend is equal to 1 (last chunk
was sent), test if the status is 424.
Logged In: YES
user_id=1357631
Fix reprot:
Purpose:
This patch is to fix Bug 1370291 for SCTS DS1.1.2
Description of the Patch
The variables FirstChunkSend and LastChunkSend are not
correctly initialized:
After setting FirstChunkSend to 0 (@ line 688), it tests
if this variable is equal to 0 (@ line 692), set it to 1
and set LastChunkSend to 0. Next time it will send the
last chunk without sending the first chunk.
And the status 424, for invalid size, is never checked.
Short overview of how the patch works
Add variable SwitchFirstLastChunk to do a correct switch.
If the variable FirstChunkSend is equal to 1 (first chunk
was sent), test if the status is 213,
else if variable LastChunkSend is equal to 1 (last chunk
was sent), test if the status is 424.