WEB TESTING

VIDEO I

There are usually two levels of architecture:

1. One level - Client => Server;
2. Two level - Client => Application Server => Database.

VIDEO II

How server communicate with user? Need to use some rules. These rules are called – Protocol.
HTTP – Hyper Text Transfer Protocol;
HTTPs - Hyper Test Transfer Protocol secured:
SSL/TLS
Public/Private key
FTP – file transfer protocol
POP3 & SMTP - mail protocols // and IMAP
UDP – user data gram protocol (streaming – not assuring to resend lost data).

HTTP – Hyper Text Transfer Protocol:

Request – from client to server;
Response – from server to client.

Structure of the HTTP request:

1. Base line (Start line):
*METHOD* URI protocol
*what* *where/with what* HTTP 1.1
e. g. GET index.html HTTP 1.1
2. HEADERS (it needed to know for forming the right answer for client):
param1: attr1, attr2, attr..attrn
param2: attr1, ..

user-agent: OS, browser…

encoding:
time-zone:
cookies:
if-modified-since: dd.. time
3. BODY (optional):

Structure of the HTTP response:

1. *status code* status message

e.g. 404 Not found
2. HEADERS (it needed to know for forming the right answer for client):
param1: attr1, attr2, attr..attrn
param2: attr1, ..
content-type: image
cookies: @#RJKHSf
last-modified: 14.01.2017 15:49:21 GTM
e.g. if last-modified is the same for client and server the BODY will be empty – 304 Not modified if not:
3. BODY:
*METHODS* for the HTTP request:
GET – is used to get information, has no body
There are 2 types of get:
1. GET catalogue.html;
2. Get with parameters:
e.g. GET index.html?lang=ru, GET catalogue.html?brand=ITVDN&partner=StartIT&category=QA

POST (used to login, registration, payments, sending messages, post etc.);

*Differences between GET and POST: GET is sending parameters through URI and it is displayed in browser address bar,
but POST send parameters through BODY requests and it is not displayed in browser address bar. That means when using
GET the info is saved in browser history. Conclusion: it is not recommended to use GET with porno like or payment info.
Pro for GET: you have a unique link(good for sending, saving
Cons for POST: the response for POST are not caches, every time need to download full info.

HEAD DELETE (is like GET)

GET says: Give me HTML catalogue, HEAD says: tell me if there is a HTML catalogue.
Response for Get has BODY, response for HEAD is: 200 ok or 404 Not Found.

DELETE: Deletes the specified resource

 VIDEO III
The five groups of server’s answers:
1xx – Info (101 switching protocols);
2xx – Success (200 OK);
3xx – Redirect (304 Not Modified);
4xx – Client error (404 Not Found);
5xx – Server error (500 internal server error, 504 Temporary not avai).

VIDEO IV (Cookies)