MT - 45 - Test scenario and Test case - Difference!

Often we get confused between test case and Test scenario. These are two important points from testing point of view :

Test Case	Test Scenario
Test Case is ‘How to be tested’	Test Scenario is ‘What to be tested’
Test case consist of test case name, Precondition, steps / input condition, expected result.	Test scenario consists of a detailed test procedure. We can also say that a test scenario has many test cases associated with it. Before executing the test scenario we need to think of test cases for each scenario.
Test cases are low level actions and it can be derived from test scenarios.	Test scenarios are the high level classification of test requirement grouped depending on the functionality of a module and it can be derived from use cases.
Each test case checks for a single functionality or test scenario.	Test scenario may have numbers of test cases.
Test case means detailed documenting the cases which help executing while testing.	Test Scenario means talking and thinking requirements in detail.
Test cases are set of steps which performed on system to verify the expected output.	Test scenario is thread of operations.
Test cases are more importance in case where development is happening onsite and QA is happening Off shored. It will help to understand and make both developer and QA in sync.	Test scenarios are more important when time to write test cases is no sufficient and team members are agree with the detailed one liner scenario.
Writing test cases is one time effort which can be used in future while executing regression test case. While reporting defects it will help tester to link the defect with test case id.	In new software testing generation it is new idea and time saver activity. The addition and modification (easy maintainability) of test scenarios is easy and independent on specific person.
The intention of test cases is to capture all the requirements. If developer missed something then it is easy to catch while executing these full-proof test cases.	One of the most positive point about test scenario is good test scenarios reduces the complexity and repeatability of product.
It requires more effort due to detailed test case which talks about how to test .	If the test scenario not detailed enough then it might take some time to discussion and understand what test scenario is exactly talking about.
Test cases has one to one relation	Test scenarios has one to many relation.
Test cases are the set of valid and invalid executable procedure of a test scenario. A test case with valid functionality is called positive test case and a test case with invalid functionality is called negative test case.	A test scenario may have one or more test cases associated to it.

MT - 44 - Error Seeding or Bee-bugging ?

Bee-bugging or error seeding is a process of intentionally adding errors to the code to evaluate the amount of residual errors during the phase of testing. In Simple language we can say that we can estimate the total error found in the application to that of the error seeded in the code. This may be used to map the testcases and the level of testcases designed. Additionally we can check that the behaviour of application after introducing errors. IN error-seeding technique a certain number of errors are sown in code while in mutation testing a change in the statement is done (Refer blog 26 for mutation testing).

Here are few differences between them

Error Seeding	Mutation Testing
No mutants are present here.	Mutants are developed for testing.
Here source code is tested within itself.	Here mutants are combined, compared for testing to find error introduced.
Errors are introduced directly.	Special techniques are used to introduce errors.
Test cases which detect errors are used for testing.	Here, test cases which kill mutants are used for testing.
It is less efficient error testing technique.	It is more efficient than error seeding	.
It requires less time.	It is more time consuming.
It is economical to perform.	It is expensive to perform.
It is better method for bigger problems.	It is a better method for small size programs.

MT - 43 - What is baseline testing?

As the name says , base-lining is defined as the standard that forms the base for any software or application.
Its a type of non-functional testing which refers to the validation of the documents and specifications on which the test-cases will be designed.In configuration management, a baseline is an agreed description of the attributes of a product, at a point in time, which serves as a basis for defining change Normally SRS is considered as the baseline of testing.
Baseline is the point at which some deliverable produced during the software engineering process is put under formal change control.Base Lining is the very important process in the Configuration Management.Once the base lining is done the application is blocked for the editing. Only after the base lining we can give the version no to the particular application.A specification or software product that has been formally reviewed or agreed upon ,that thereafter serves as the basis for further development,and that can be changed only through a formal change control process.he point at which some deliverable produced during the software engineering process is put under formal change control.