Test Case Design

A test case design is a detailed procedure that fully tests a feature of the software application or an aspect of a feature, depending on the complexity of the application..this describes the various permutation and combination of steps to be carried out to test a feature.

Normally Test Case Design is done in two way.
1. Descriptive: These test cases contains information on how to perform the test and the data that should be used to perform the test

2.Detailed: These test cases describes the manner in which the test should be performed.
In general every organisation try to opt Detailed test cases, because these are reproducible and can be automated easily and can be used to determine the pass and fail criteria for test.

Few things need to be included while test case design
1. Identify the test case and explicitly associating it with feature to be tested.
2.Mapping test cases with requirements by using requirement traceability matrix.
3. Purpose of the test.
4.Creating a list of specified criteria for which the test should be tested.
5.Creating a list of tests that should be excercise as a consequences of test.
6.Assembling of expected results occure,when test are executed
7.Creative scenario, or conditions in which tests are executed.
8.Assimilate all information that add value to understand the test.
Since test case designing is time consuming. However, if this activity is done extensively then it enables tester to find goal of testing with in time.

A test case also includes certain things that is very important in a sucessful testing.
1. Purpose of testing.
2. Hardware and software environment required.
3. Special configuration requirement like making war room.
4.Detail of the testing processes.
5.Expected results or success criteria of test.

 

Difference Between Black box and White box Testing

Difference Between Black box and White box Testing

Black-Box Testing
1- Black Box means opaque object or box where we can’t see the internal structure.In Black box testing
we only concentrate on Input and output.2- Black-box test design is usually described as focusing on testing functional requirements. So we normally test
the functionality of software without going deep in to its code and structure3- Techniques that is used in Black Box testing

  1. Boundary-value analysis
  2. Error guessing
  3. Race conditions
  4. Cause-effect graphing
  5. Syntax testing
  6. State transition testing
  7. Graph matrix
  8. Equivalence partitioning

4- Best example of Black box testing is Search on Google. User just enters keywords and get the expected results in turn.
End user never take tension to see what is behind this screen that is employed to fetch these results.
5- Technical background is not the necessity of Black-Box Tester.Black box and White box testing

 

White-Box Testing
1- White-Box testing is also known as clear box testing, glass box testing, transparent box testing, and structural testing.
2- White-Box testing deals with the internal structure and the internal working rather than only functionality.
3- For White-Box testing, programming background is must because this helps in creating test cases for white-box testing.
4- White-box testing is applied for Unit testing, integration testing and sometime in it is also used for system testing.
5- These are few techniques that are used in white box testing

  1. Code Coverage
  2. Segment coverage: This is done to ensure that all statement or each line of code has been executed
  3. Compound condition coverage and loop coverage: In this we test all the conditions and all the branching and loops in code
  4. Data Flow testing: we test all the intermediate steps, in this we test how sequential steps behave
  5. Path Testing: In this we test all the path that is defined in code

6- Through White-Box testing, tester detects all logical errors, design error and Typographical error.

What is Manual testing

What is manual testing?

Manual testing is just the software testing which is normally done manually to detect bugs. In this testing, testers act as end user and try to touch all features to ensure that software is fulfilling all the requirement of Client or the need of software.

Manual testing is normally done in the initial phase of product development when is not enough stable. Once we get the stability in the functionality of software, we think about Automation of test execution.

Manual testing is gives freedom to tester for Ad-hoc testing and this increases the chances of finding more and more bugs in initial stage of software development. Manual testing is like playing with software to break it and also a chance to be familiar with all functionality of a software.

In general we can say that Manual testing is the first step of testing and automation follow it when product get stable . One more thing bigger the project, bigger the role of manual testing so we can say that manual testing have a good part in term of percentage in testing rather than automation testing, no due to its ease but also due to the cost.

Procedure involves in manual testing

1- Making a good test plan that includes all the overview,scope, methodologies and also the resources
2- Writing test cases with the help of SRS and on the basis of Use-Cases
3- Review of test cases is done to make sure that all functionalities are covered and nothing is left for writing test cases
4- Execution of test case(Dynamic testing)
5- Detecting Bugs
6- Filing bugs in Bug tracking tools like Bugzilla
7- Making test report
8- Retrospection of the whole process.

1 43 44 45 46 47 48