Cache Testing for any Mobile, Cache Testing Test
Cases for Mobiles
Cache sits between multiple or web servers and
multiple clients or a client, and watches request come by. Saving
copies of the replies – like images and files, HTML page
(Collectively known as the representations) – for itself. Then if
there is some other request for the quite same url. The it can be use
the reply that it has instead of asking the main server for it again
and again. That's all!
Cookie information is being checked using proxy
server logs like the one below...
Set-Cookie :
Cookie = Hello’; Path=’/’; domain=’Server’
Following are the Test Cases for Cache Testing for Mobiles:
Test
Category
|
Conformance
|
|
Feature/Requirement
|
Interpreting
Set-cookie
|
|
Reference
|
RFC -2109
|
|
Test
Description
|
To verify
the interpreting of UA on Set-cookie received from origin server
|
|
Test
Setup
|
Precondition:
Cookie
should be cleared and set in the client
‘Cookie
Proxy’ option should be disabled
Disable
the cache
|
|
Different
test inputs
|
||
Test
Approach
|
||
Action
|
Response
|
|
1. Fetch
http://Server/start.html
|
The
requested page is fetched.
|
|
2. Enter
Cookie name ‘Hello” to send and click Submit
|
Page is
displayed with Cookie name Sent to browser from server.
Check in
Proxy logs :
Set-Cookie
: Monster = ‘Hello’; Path=’/’
|
|
3. Click
on first link “Click here to continue” to send receive cookie
to server
|
Page is
displayed.
Check in
Proxy logs :
In Get
request client sent the request header with cookie.
Cookie:
$Version=1; Monster=’Hello’ Path=’/’; Domain=’Server’
|
|
Expected
Result
|
Client
should receive Cookie value from Set-Cookie server response and
should send same value to server to continue session for
subsequent request under same path mentioned in ‘Set-Cookie’.
|
|
Actual
Result
|
||
Status
|
||
Tester’s
Notes
|
||
Test
Outputs / Data Logs
|
||
Executed
By
|
||
Execution
Date
|
||
Test
Case id
|
2
|
|
Test
Category
|
Conformance
|
|
Feature/Requirement
|
User Agent
Keeps separate track of State information that arrives via
Set-Cookie response header from each origin server (as distinguish
by domain and IP)
|
|
Reference
|
RFC -2109
|
|
Test
Description
|
To verify
that UA keeps separate track of state information as as
distinguish by domain and IP
|
|
Test
Setup
|
Precondition:
Cookie
should be cleared and set in the client
‘Cookie
Proxy’ option should be disabled
Disable
the cache
|
|
Different
test inputs
|
||
Test
Approach
|
||
Action
|
Response
|
|
1. Fetch
http://Server/start.html
|
The
requested page is fetched.
|
|
2. Enter
Cookie name ‘Hello 41” to send and click Submit
|
Page is
displayed with Cookie name Sent to browser from server.
Check in
Proxy logs :
Set-Cookie
: Monster = ‘Hello 41’; Path=’/’
|
|
3. Fetch
http://203.200.36.36/start.html
|
The
requested page is fetched.
|
|
4. Enter
Cookie name ‘Hello 36” to send and click Submit
|
Page is
displayed with Cookie name Sent to browser from server.
Check in
Proxy logs :
Set-Cookie
: Monster = ‘Hello 36’; Path=’/’
|
|
5. Click
on first link “Click here to continue” to send receive cookie
to server
|
Page is
displayed.
Check in
Proxy logs :
In Get
request client sent the request header with cookie.
Cookie:
$Version=1; Monster=’Hello 36’ Path=’/’;
Domain=’203.200.36.36’
|
|
6. Fetch
http://Server/cgi-bin/cooki_test.cgi
|
Page is
displayed.
Check in
Proxy logs :
In Get
request client sent the request header with cookie.
Cookie:
$Version=1; Monster=’Hello 41’ Path=’/’; Domain=’Server’
|
|
Expected
Result
|
User
Agent should Keep separate track of State information that arrives
via Set-Cookie response header from each origin server (as
distinguish by domain and IP)
|
|
Actual
Result
|
||
Status
|
||
Tester’s
Notes
|
||
Test
Outputs / Data Logs
|
||
Executed
By
|
||
Execution
Date
|
||
No comments:
Post a Comment