Build verification testing

Build verification Testing:

            Build verification testing is also called as smoke testing.Build verification is a set of tests run on new build to verify that whether the build is application to proceed for testing.It is done priorly by test team before releasing  application to testing.This testing is mainly done for build validation and build acceptance.This test is done for each new build  if any of tests got failed that build is rejected by testing team.
Below is the process for Build verification testing:
        ·     The results are sent to TL / PM

·     Results are analyzed by TL / PM

·     The person who runs the tests and TL / PM diagnoses the cause of failure (if any)

·     If there is any defect, the relevant information is sent to respective developers

·     Developer fixes the bug

Once the bug is fixed; BVT test suite is executed again. This process gets repeated for every new build.

How to see cookies files

step 1: Open IE
step 2: click the tools menu->Internet options
step 3: Click general tab->search for browsing history which is under home page information
step 4: From browsing history click settings
step 5: In that window you will get three events a)move folder b) view objects c)view files
step 6: Click the view files you will get the temporary files which is the cookies files 

Cookies Testing

 Below is a list of major scenarios for cookies testing of a website. Multiple test cases can be generated from 

1.                   Check if the application is writing cookies properly or not.

2.                  Test to make sure that no personal or sensitive data is stored in the cookie. If it is there in cookies, it should be in encrypted format.

3.                  If the application under test is a public website, there should not be overuse of cookies. It may result in loss of website traffic if browser is prompting for cookies more often.

4.                  Close all browsers, delete all previously written cookies and disable the cookies from your browser settings. Navigate or use that part of web site which use cookies. It should display appropriate messages like "For smooth functioning of this site please enable cookies on your browser."

5.                  Set browser options to prompt whenever cookie is being stored / saved in your system. Navigate or use that part of web site which use cookies. It will prompt and ask if you want to accept or reject the cookie. Application under test should display an appropriate message if you reject the cookies. Also, check that if pages are getting crashed or data is getting corrupted.

6.                  Close all browsers windows and manually delete all cookies. Navigate various web pages and check and see if these web pages show unexpected behavior.

7.                  Edit few cookies manually in notepad or some other editor. Make modifications like alter the cookie content, name of the cookie, change expiry date etc. Now, test the site functionality. Corrupted cookies should not allow to read the data inside it.

8.                  Cookies written by one web site should not be accessible by other website.

9.                  If you are testing an online shopping portal, Check if reaching to your final order summary page deletes the cookie of previous page of shopping cart properly and no invalid action or purchase got executed from same logged in user.

10.               Check if the application under test is writing the cookies properly on different browsers as intended and site works properly using these cookies. This test can be done on browsers like different versions of internet explorer, Mozilla Firefox, Netscape, Opera etc.

11.                If the application under test is using cookies to maintain the logging state for users. Check if some id is being displayed in the address bar. Now, change the id & press enter. It should display an access denied message and and you should not be able to see other user's account.