Skip to main content

TestCases - Q/A

1. What is a Test Case
Test Case is a document which describes the pre-requisite of input action and an expected result to validate that feature of the system/application is working correctly or not.

2. What do you mean by Test Cases?
Test cases typically describe test inputs, execution conditions, pre-requisite, expected result and actual result.

Known Input :-: Pre-Condition
Expected Output :-: Post Condition

3. Why do we write Test Cases?
 We have not one or two benefits of writing test cases, but we have lots of things to get a application bug free, when we jot down the test cases in the document from the process of thinking. It increase the efficiency of executing tester, as many as possible bugs can be found out in earlier phases of testing. Testing is not too simple neither too complex. 

Note: But for every single test case we have should only one expected result.
Test cases is implemented to validate the Application / Product is performing in the intended behavior. 

4. How to write test cases?
The basic objective of writing test cases is to validate all the requirement of the application. It will minimizes the Ad-Hoc approach in testing.

5. What is the difference between positive and negative test cases?
For each and every requirement we have at least two test cases - 1. Positive and 2. Negative test cases. This can be achieved by techniques used for writing test cases like Boundary Value, Equivalence Partitioning.

6. How will you check that your test cases covered all the requirements?
Relationship between Test cases and Requirements when clubbed together the another very important document is created known as Requirements Traceability Matrix

Comments

Post a Comment

Popular posts from this blog

Application Lifecycle Management

Application Lifecycle Management Lifecycle the word means “Series of stages through which something passes during its lifetime.” Application lifecycle is similar to giving birth to a young one as per the God’s management. Creating an application is not a big task, but adding the word Management in that Application  Lifecycle is adding a process of distributing with or governing things or people.  When Process comes in a picture, we bound to work according to that, which give the  picture of Application Lifecycle Management. Accumulation process is not that you are bound to move in that particular line only, but it  means you are moving in the correct direction which will give success and 99.9%  assurance that the Project on which you have implemented is having a correct planning,   great controlling, and using the resources in an organized behavior. Application Lifecycle Management is controlling of a software application from planning...
Post a Comment
Read more

What do we mean by Usability?

Many definitions of usability are available, few of them are: 1) In simple words it is "The ease of use". 2) It is the amount of effort required in learning, operating, preparing inputs, and interpreting the outputs of an application. 3) Technical definition prescribed in ISO 9241-11 is: "The extent to which a product can be used by specified users to achieve specified goals with Effectiveness, Efficiency and Satisfaction, in a specified Context of use".  This testing is also called as 'Testing for User-Friendliness'. This testing is done if User Interface of the application stands an important consideration and needs to be specific for the specific type of user. Usability testing is the process of working with end-users directly and indirectly to assess how the user perceives a software package and how they interact with it.    This process will uncover areas of difficulty for users as well as areas of strength. Usability "means...
3 comments
Read more

Project Estimation Template

  Read Me All white cells are editable in the estimation template Estimation Summary 1 In this sheet, mention the basic project information. 2 This sheet gives the amount of effort estimated for each phase, based on the effort distribution. 3 ‘Engineering effort’ is the total amount of effort estimated for the project 4 Total Size (complexity Point) is the calculated value of the complex points or the size of the work that has to be performed. 5 ‘Project Management Effort’ is the percentage of Engineering Effort that will be required for project management. 6 ‘Total Effort (Hours)’ is the sum of ‘Engineering Effort’ and ‘Project Management Effort’ 7 ‘Contingency %’ is the percentage of total effort that counts for an incidental expense 8 ‘Grand Total Effort (Hours)’ is the sum of ‘Total Effort (Hours)’ and ‘‘Contingency %’’ 9 ‘Assumptions’ and Risks: List all the assumptions and risks related to estimation Estimation Criteria 1 Mention the criteria for various complexities i.e. Low...
Post a Comment
Read more