The Art of Programming

Bug's Life Cycle - [Image source: http://www.bughost.com] As a tester tests an application and if he/she finds any defect, the life cycle of the defect starts and  it becomes very important to communicate the defect to the developers in order to get it fixed , keep track of current status of the defect, find out if any such defect (similar defect) was ever found in last attempts of testing etc. How to report a bug? It’s a good practice to take screen shots of execution of every step during software testing. If any test case fails during execution, it needs to be failed in the bug-reporting tool and a bug has to be reported/logged for the same. The tester can choose to first report a bug and then fail the test case in the bug-reporting tool or fail a test case and report a bug. In any case,  the Bug ID that is generated for the reported bug should be attached to the test case that is failed. Tagging or naming the bug with the Unit or integration test will aid developers to

The main difference between persistent cookies ( or simple cookies ) and session cookies (or simply sessions) are that cookies are stored in the user's browser, and sessions are not. This difference determines what each is best used for. “A cookie can keep information in the user's browser until deleted. If a person has a login and password, this can be set as a cookie in their browser so they do not have to re-login to your website every time they visit. You can store almost anything in a browser cookie. The trouble is that a user can block cookies or delete them at any time Sessions cookies are not reliant on the user allowing a cookie. They work instead like a token allowing access and passing information while the user has their browser open. The problem with sessions is that when you close your browser you also lose the session. So, if you had a site requiring a login, this couldn't be saved as a session like it could as a cookie, and the user would be for