Ans: This is the document specifying scope, approach, resources and schedule of intended activities.

Ans: When a bug is found first inform it to team leader, if he say yes then add this bug to bug tracking tool.

Ans: Verification: The process of evaluating software to determine whether the products of a given development phase satisfy the conditions imposed at start of a phase.
Validation: The process of evaluating software during or at end of development process to determine whether it satisfies specified requirements.

Ans: In software testing, smoke test is collection of that are written on a system prior to being accepted for further testing. This is also called as build verification testing.
Smoke testing can be performed manually or by automated tool.

Ans: The bug, changed to deferred state means the bug is expected to be fixed in next releases. There may be several reasons for changing the bug to this state. Some of them are priority of bug is low, lack of time for release or bug may not have major effect on software.

Ans: Agile testing is a software testing practice that follows the principles of agile software development. Agile testing consists of number of cross functional agile team, with special expertise contributed by testers, to ensure delivering the business value desired by customers at frequent intervals, working at sustainable pace. Specification by example, also known as acceptance test driven development.

Ans:Tests for system software requirements using Trace Matrix, cross-functional testing and decision table.

Ans: If possible tests are automated or else, execute only test cases which are mandatory.

p { margin-bottom: 0.21cm; } Ans: The possible input conditions are: Input password as= 6abcde (number first) Input password as= abcde8 (character first) Input password as= 123456 (all numbers) Input password as= abcdef...  

Ans: The length of test case totally depends on application.