v model??
BRS Acceptance testing
SRS SystemTesting
HLD System Integration testing
LLD Component Testing
Coding Unit Testing
2.Equivalence partioning and boundary value analysis....???
Equalance partion is a method of black box testing.for eg if the application is accept the values between 10 to 50.we are giving valid and invalid inputs to the system and check the status.
eg inputs valid:25,30
invalid:9,60
boundary value analyses also method of blackbox testing,in this case we r taking boundary vaues for eg in abouve eg upper boundary value is 50,and lower boundary value is 10.
inputs
upper boundary 49,51.
lower boundary 9,11
on boundary 10,50
3.Test plan and test strategy.....????
A Test Strategy document is a high level document and normally developed by project manager. This document defines “Testing Approach” to achieve testing objectives. The Test Strategy is normally derived from the Business Requirement Specification document.
Components of the Test Strategy document
Scope and Objectives
Business issues
->Roles and responsibilities
Communication and status reporting
Test deliverability
Industry standards to follow
Test automation and tools
Testing measurements and metrices
Risks and mitigation
Defect reporting and tracking
Change and configuration management
Training plan
The Test Plan document on the other hand, is derived from the Product Description, Software Requirement Specification SRS, or Use Case Documents.
The Test Plan document is usually prepared by the Test
Lead or Test Manager and the focus of the document is to
describe what to test, how to test, when to test and who
will do what test.
-->Test Plan id
Introduction
Test items
Features to be tested
Features not to be tested
Test techniques
Testing tasks
Suspension criteria
Features pass or fail criteria
Test environment (Entry criteria, Exit criteria)
Test delivarables
Staff and training needs
Responsibilities
Schedule
4.Tabs in quality center?
There are 5 tabs in Quality Center.
1. Releases-To specify the release details.
2. Requirements-To specify the requirements related to
releases.
3. Test Plan-Test Cases Designed.
4. Test Lab-Test Cases Execution.
5. Defects-Log and track defects.
5.How to map requirements to testcases??
Step1- Select the test cases from Test Plan tab in QC.
Step2- Select "Requirement Covg" tab, it will show option for "Add requirement( an umbrella symbol)"
Step3- Click on that "Add Requirements" option, it will open Requirements pane at right hand side.
Step4- Select the appropriate Requirements and click on ok.
(Sometimes it will ask to add requirements with its child contents, then u may add it.)
6.How to map defects to testcases??
Test Cases are generally mapped with defects by going to the Defect mapping icon at the top of the running test set, generaly a red baloon like structure, also, u can create a new defect when the test case is faiing or you can add one exisiting defect by specifyig its id.
A defect can also be mapped in test lab failed test case from Defects module, mapping the same as specifying above.From tes lab-- go to Linking/ Coverage-- go to Defects..
map the id or create a new defect.
7.Smoke and sanity testing
Smoke Testing:
Software Testing done to ensure that whether the build can be accepted for through software testing or not.Basically, it is done to check the stability of the build received for software testing.
Sanity testing:
After receiving a build with minor changes in the code or functionality, a subset of regression test cases
are executed that to check whether it rectified the software bugs or issues and no other software bug is introduced by the changes.Sometimes, when multiple cycles of regression testing are executed, sanity testing of the software can be done at later cycles after through regression test cycles. If we are moving a build from staging / testing server to production server, sanity testing of the software application can be done to check that whether the build is sane enough to move to further at production server or not.
8.Differences b/w Delete and truncate??
TRUNCATE
1. It is DDL.
2. Speed is faster
3. Do not Check Constraints.
4. Roll Back is not possible.
5. Can not use where clause
DELETE
1. It is not a DDL
2. Speed is slow
3. Check constraints, If Exists then shoe error.
4. We can rollback .
5. User Where Clause.
9.Priority and severioty??
1.High severity & low priority :- If a application crashes on very rare occasions and changes are very low of crashing.so severity will be high but priority will be low.
2.High severity & high priority:- if a application crashes very frequently and duly visible or first time the application came from development team to the testing department.
3.Low severity & low priority:- it is merely just a enhancement bug which the client wishes like changing the background colour of user interface,also like adding a button like 'back' to navigate previous page.
4.Low severity & high priority:- In this case if the name of the company on its home page is misspelt will be considered. So to find that in which category the bug comes always remember one thing that Low severity bugs are mostly related to GUIs and high severity bugs always related to things like
system crash.severity is always technical while priority isfor business purpose.
10.Star schema and snow flake schema??
star schema
1.It can be analysed only in 16 dimensions. 2.Master data is not reusable. 3.performance is degraded because of the alphanumeric values in the fact table.
Extended Star Schema 1.It can be analysed in 16*248 dimensions. 2.Master data can be reusable as it is not inside the cube. 3.Better performance as there r no alphanumeric values in the fact table.
