3:3

1.Database tetsing???

The method you want to test executes a rather large JOIN operation and uses the data to calculate some important results. Your business logic performs a mix of SELECT, INSERT, UPDATE and DELETE statements. You need to setup test data in (possibly much) more than two tables to get reasonable initial data for the methods you want to test. The DbUnit extension considerably simplifies the setup of a database for testing purposes and allows to verify the contents of a database after performing a series of operations. Sample test case for database testing: The test case for the above requirement is mentioned below: Test_Case_Id:1 Test_Case_Name:Check the unique identity of Student. Description:Test case to check the unique identity of Student. Prerequisite: 1.Database should be present 2.Student records should be present in student table. Input Data:1.Open your database(SQl,oracle or any which you are using) 2.Open its command prompt editor. 3.Select the proper database 4.Enter the query as:"Select * from Student_Details" 5.Run the query. Expected Result: The all unique student records will be displayed. Validation:Student is should be unique.

2.What is Facets testing ??

Facet means small small aspect or attributes.All the filter criteria options can come under
facets,testing of these size,name,contains is called as facet testing.

3.How we Check Perfomance testing In Manual?

If there is a back end database to the Web app you can use the database Performance analyser

tool to evaluate the same.General web apps are performance tested in terms of the time taken 

to load a page. This is manually timed using the systems clock.

For client server apps : The performance c/s apps is manually checked again using the systems

clock to validate the server response to a client request.The above tests are done only for fine 

tuning purpose of the applications.If the performance under load is to be tested a use of tool 
is essential.

Continue lendo

Three Three

1.Differences between smoke,sanity,regression and Retesting???

SMOKE TESTING: TESTING DONE TO CHECK WHETHER THE BUILT  RELEASED IS STABLE ENOUGH FOR FURTHUR TESTING OR NOT  SO THIS IS THE FIRST IN OUR LIST.

RETESTING: ONCE THE BUG IS FIXED THEY RETEST THE FEATURE TO VERIFY THE BUG IS STILL PRESENT OR NOT.SO THIS WILL COME 2ND IN LINE.

REGRESSION TESTING:TO VERIFY THE BUG FIX DINT EFFECT
ALREADY WORKING FEATURES. SO THIS ID 3RD IN THE LINE

SANITY:IN MOST COMPANIES SMOKE/SANITY USE AS ONE BUT

SANITY TESTING IS TO VERIFY THE APPLICATION WHICH THEY R
GONNA RELESE SOON IS  STABLE WHITOUT ANY CRITICAL BUG.

DIFF BETWWEN SMOKE AND SANITY IS THE TIME THEY R TESTED.

2.Entry and Exit criteria?
Entry Criteria:
1 All code of application, unit tested.
2 Test plan, test cases reviewed and approved.
3 QA/Tester get significant knowledge of application.
4 Test environment/test ware get prepared.
5 After getting application build.
Exit Criteria:
Deadlines (release deadlines, testing deadlines, etc.)
Test cases completed with certain percentage passed
Test budget depleted
Coverage of code/functionality/requirements reaches a
specified point
Bug rate falls below a certain level
Beta or alpha testing period ends.



3.Testing process.....
Project finalized
Requirement analysis
Formal meeting with team members
Writing test cases
Review of test cases with developers
Test environment setup
Executing testcases
Bug Anatomy
Bug reporting
Regression testing
Retesting
Sanity testing
Test closure report
sign off.

 

Continue lendo

3 : 3

1.What is Risk and mitigation plan?????
Project Manager is responsible for preparing Risk Mitigation strategy. However, he might would like to take inputs from the project team leads/members, BAs, QA, SQA
and IT infrastructure support teams to come up with an effective mitigation plan.


Mitigation has to do with devising one or more approaches to control, avoid, minimize, or otherwise mitigate the risk. Mitigation approaches may reduce the probability or the impact. It is more of a PROACTIVE initiative even before the risk becomes a problem.


The objective of a mitigation should be to ensure a risk identified doesn't occur or the least reduce it's probability of occurence.


Contingency plan on the other hand has to do with what if you are hit by the problem for the risks you could not mitigate. (This is in contrast a REACTIVE mode).

2.When to stop testing?????
When to stop testing" is one of the most difficult questions to a test engineer. The following are few of the common Test Stop criteria:


- All the high priority bugs are fixed.
- The rate at which bugs are found is too small.
- The testing budget is exhausted.
- The project duration is completed.
- The risk in the project is under acceptable limit.


3.What is bug reproduce?????
You can reproduce a Bug during Regression testing.There is nothing like a 'Reproduce' state in Bug life cycle as the Bug life cycle starts at finding a bug and end when the defect is retested successfully to close/end bug life cycle.Usually bugs can be found during regression testing which would have caused due to a fix in some other functionality.

 

Continue lendo

3 : 3

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.

 
 

Continue lendo

SP - concepts

Test Delevirables ???
Before Testing Test Deliverables include Test Plan, Test Strategy, Test Scripts (Includes Test Case and Expected Result) and Test Execution Schedule.
After Testing Test Execution Report, Traceablity Metrics, Defect Reports and Test Report.


2.Test completion report???
As a tester,I will submit the TEST COMPLETION REPORT as
final report.
In this report we need to mentioned,
How many test cases we have
How many test cases we executed
How many test cases we passed
How many test cases we failed
How many test cases Unable to Run
total number of defects raised
toal number of defects resolved
total number of defect still outstanding
total number of defects rejected
we can get these details in reports from quality center
with charts.
and also availability of environment,is there any problem
we are doing execution
Any issues are there.
is there any regression testing required for this project.
these details we will put in Test completion Report then
send it to the Test Manager.
 
3.Regression testing types??
mainly two levels of regression testing is available .
1) regular regression
2) final regression
In regular regression every  built is tested to verify
weather the fixed bugs have any bad impact on other parts
of the functionalities.It is done regularly during the
testing process evry after getting new built.
Final regression is done after the complition of fixing
all the bugs.It is advisible to have stable built during
Final regression testing


4.Mapping Requirements with testcases??
You can trace relation between test cases, requirements and defects -
1) When you raise the defect the test case number is available in the defect.  The function name is also available in the defect detail.
2) While writing the test cases the Requirement specification version is mentioned in the test case header part.
The refrence of requirement can be specified in the Test cases.
The refrence of Test case number can be specified in the Defects.

Continue lendo

ETL testing concepts

Business understanding

a. High Level Test Approach

b. Test Estimation

c. Review Business Specification

d. Attend Business Specification and Technical Specification

walkthroughs.

2) Test plan creation, review and walkthrough.

3) Test case creation, review and walkthrough

4) Test Bed & Environment setup

5) Receiving test data file from the developers

6) Test predictions creation, review (Setting up the expected results)

7) Test case execution and (regression testing if required).

a. Comparing the predictions with the actual results by testing the

business rules in the test environment.

b. Displaying the compare result in the separate worksheet.

8) Deployment

a. Validating the business rule in the production environment

Continue lendo

software police concepts 1

Severity and priority with examples


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 is for business purpose.


2.Is testcases compulsary ????

Test case is a Step by step procedure  to validate the functionality of the system. The important
reason why it should be documented is,

1. Testing all the fnctionality is a repeated process and can be executed any number of times in future. So the plan is to Execute all the cases with out fail.

2. The testcase may be executed by any other tester. So rework is avoided.

3. To keep track/cover all the possible functionalities.

3.What is test strategy ??


Test strategy is an organisational level term and it is used for all the projects in the company.
the contains contains contains the followinf items


1.levels of testing
2.types of testing
3.test design techniques
4.configuration management
5.test metics
6.automation plan
7.list of automation tools
 
 

Continue lendo

Miscellaneous......Week 1

1.Why do u choose software testing as your career??

I am interested in software testing because, the developer may develop an application with his knowledge, but the tester have the ability to test the functionality, performance and quality of the application and to test whether the application is user friendly and whether it satisfies the user requirements, so the tester decides the  Quality of the application. so i choose this field.

2.what is defect duplication??

Before raising the defect all the testers must search in existing defects by specifying defect description.This will avoid duplication.If they find an existing defect which is
related to his issue, they can link the defect to his script.

3.What is port testing and Mutation testing ???

Port testing is installation testing,its performed after user acceptance testing.Project management define release team along with few developers and hardware engineer and tester,Release team conducting PORT Testing in corresponding customer environment.During this testing release team
conducting following factors :



1)all files are installed or not
2)Memory occupied by the system
3)Supported software's are installed or not
4)O.S error handling

Mutation testing :
The application is tested for code that was modified after fixing a particular defect.It helps to
find which code/stategy of coding can help in developing the functionality effectively.

4.What is agile testing ??

Agile Testing is preferable with Agile Model.When the Requirement is changes frequently or Unstable then we need to perform Agile Testing.According to this Tester will work closly with Developer and Testing had been done before every release.Release may b scheduled on daily basis or once in 2/3 day.So Tester will do the Testing accordingly.
 
5.What is configuration management??

Configuration mangement nothng but maintaing and tratcking the files which are saved.Normally organisations use VSS as configuration mangement tool.VSS is a abbreviated asa visual source safe.Its a version control tool.After completion of developing the completion the build will be stored in vss.The file willnot editable after saving the file into VSS.Here we  Check In /Checkout Process to Upload/Download the Files.After Check out then only u can modify the files/ Documents.After that the tester will CHECKOUT and save the same file for testing.The VSS will be useful to a tester like sending his testcase for review and storing his documents and sending the bug reports to testlead

Continue lendo

Situations

1.There are 3 mandatory fields and 3 optional fields :

How many possible testcases can be written?

How many positive testcases can be written?



1)Leave blank 3 mandatory fields

2) Leave blank 2 mandatory fields

3) Leave blank 1 mandatory fields
Comment: for 1,2 and 3 valid error message need to displayed.


4) Leave blank 3 optional fields

5) Leave blank 2 optional fields

6) Leave blank 1 optional field


Comment:

-use 4,5 and 6 entering all the mandatory fields. Without error message task
should be performed

-use 4,5, and 6 along with above 1,2, and 3 test cases. Respective error message
should display.


7) Enter all the mandatory fields and all the optional fields

Comment: Task should be performed.


8) Enter all the mandatory fields and no optional fields

Comment: Task should be performed.


.

Continue lendo

Database testing

1.Generally used SQL commands for testers.

The Transact-SQL commands most often used by a tester are:

USE database_name SELECT column_names FROM table_name

SELECT DISTINCT column_name FROM table_name'
SELECT column_name FROM table_name WHERE condition
SELECT column_name FROM table_name WHERE condition1 AND condition2
SELECT column_name FROM table_name WHERE condition1 OR condition2
SELECT column_name FROM table_name WHERE column_name IN (value1, value2, ...)
SELECT column_name FROM table_name WHERE column_name BETWEEN value1 AND value2
SELECT column_name FROM table_name WHERE column_name LIKE pattern
SELECT column_name FROM table_name WHERE condition ORDER BY column_name [ASC, DESC]
SELECT AVG column_name FROM table_name
SELECT COUNT column_name FROM table_name
SELECT MAX column_name FROM table_name
SELECT MIN column_name FROM table_name
SELECT SUM column_name FROM table_name
SELECT column_name1 SUM column_name2 FROM table_name GROUP BY column_name1
SELECT column_name1 SUM column_name2 FROM table_name GROUP BY column_name1 HAVING arithmetic function condition
SELECT table_alias.column_name1 column_alias FROM table_name table_alias
SELECT table_alias.column_name1 AS column_alias FROM table_name AS table_alias

SELECT column_names FROM table_name1 JOIN table_name2 ON table_name1.join1 = table_name2.join2 WHERE conditionSELECT column_names FROM table_name1 INNER JOIN table_name2 ON table_name1.join1 = table_name2.join2 WHERE conditionSELECT column_names FROM table_name1 OUTER JOIN table_name2 ON table_name1.join1 = table_name2.join2 WHERE condition INSERT INTO table_name (column1, column2, …) VALUES (value1, value2, …) UPDATE table_name SET column1 = “new_value” WHERE conditionUPDATE table_name SET column1 = “new_value” WHERE condition1 AND condition2UPDATE table_name SET column1 = “new_value” WHERE condition1 OR condition2

DELETE FROM table_name WHERE condition

2.Now suppose i have 50 records of employee table.
1) I want to find the person who is having 22nd highest salary.

2)i want to delete a person with postion number 39 with comminsion < 100

3) Update rec no 45 records are not shown.How do i do it.?


First question:

select min(salary) from (select distinct salary from employee order by salary desc) where rownum<=22);
or
select max(salary) from (select distinct salary from employee order by salary asc) where rownum<=22);

second question:

delete from employee where emp_id=39 and comm<100;

Third question

update table employee set recno=45;


3.When QA will use casestatement(sql query) in etl testing or datavalidation testing , like how he will be writing that Query to test the date validation.


Select * from EMP where EMP_DOJ = 010110

Here

EMP is the Table name,EMP_DOJ is the date of joining of the Employee in EMP table.

If any record/records found with DOJ as 010110,it will retrive all the records in the EMP table.
Now you need to compare the front end values with back end values with respect to corresponding record.

Note :some times Back end fields are storing for Date filed like "DDMMCCYY",but front end shows only "DDMMYY".

DD = Date
MM = Month
CCYY = Current year(2010 - Full year)
YY = Year(10 - Last 2 digits).

For above situation you need to identify the Date field format whether it is accepting "DDMMYY" or "DDMMCCYY"

Continue lendo

Differences.....

Test scenario and Test case :


Test scenario is set of test cases that ensure that the business process flows are tested from end to end. They may be independent tests or a series of tests that follow each other, each dependent on the output of the previous one.

A test case is a set of conditions or variables under which a tester will determine if a requirement or use case upon an application is partially or fully satisfied. ...

For Example :

Test Scenario  -  User Login
Test Condition -  User name max length is 8 chars and
password must not be greater than 8 char's and it should be
alphanumeric.

Test Case - 1.Enter valid username and password. 2.Enter Invalid username and valid password 3.Enter valid username and invalid password 4.Enter invalid username and invalid password.



Test bed........Test environment.........Test lab


Test bed: Sets of Test data which needs to be required set- up on the Test environment. Mean setting of data on test environment. Some time Test environment also called the Test Bed.

Test Lab: Setting up the lab with required hardware and software for testing purpose. E.g. Network lab in which also devices like Modem, Splitter, Port etc are set-up.

Test environment: in which the testing will be happened. There should be different environment like development environment or testing environment. Developer will be uploading the same code into testing environment.


Test case and Use case.....

USE CASE: Use case describes the specific action done by the user (actor) upon the system to achieve certain predefined task. Use case is done in terms of the actor. It deals with the steps followed by the user to acomplish the task.It has no matter with the input data. Use case can solve the integration defects between different component while used by the actor. Use case designed from URS.

TEST CASE: Test case is the combination of the Test conditions and Test data.It simply visualize the a particular task with a set of input data and expected output and certain test conditions. Test case is designed from SRS .



Use case........Test scenario..........Testcase.............Test suite

Use Case:
Use case are the documents that are made by the business analyst. In this document business analyst describes all the requirements on the basis of business needs.

Test scenario:

Test scenario specify all the functionality of the application that need to be tested

Test Case:

Test case specify all the steps that are need to test the functionality
Test Suite:

Group of test cases are called test suite.

Continue lendo

concepts

Web Testing Methodologies:

Web testing is very important for any internet application to run successfully. Most of the web applications fail over the time because any web application accumulates data and tends to get more number of visitors as time passes. So in order to prevent any unexpected embarrassing situations, a web application needs to be tested thoroughly for load balance testing, endurance testing and stress testing.


1) What are the important things to consider while testing a website or web application?
Answer: First of all we need to test hardware settings, server information such as hard disk space, internet bandwidth, ram size, cache size, what browser we are using to test and is the software application is compatible to that? And software hardware versions, latest patches installed or not? Video codex resolution etc..


2) What are the most important compatibility issues that may occur while testing a website?
Answer: Browser settings, font issues, browser versions, because some application may support older version or only newer versions so the programmer should check in his unit testing. This is not a tester issue, but a tester should point it out in the meetings or file a defect in defect tracking tool.


3) What are the common browsers we should take care while testing?
Answer: Mozilla Firefox, I.E, Opera etc..


4) Difference between static and dynamic web sites?
Answer: Static web sites are only informative, they are not interactive to the user of the website, i.e we cannot enter any form field values, no log in form, nothing. Only material or information to study..
Where as a dynamic web site is like http://www.mail.yahoo.com. You need to enter user name, password to log in. once u enter the website takes the values and check in the database if the credentials are right or wrong so all this is dynamic that’s why it is dynamic website.


5) Tell me something about performance testing for websites?
Answer: This is most important aspect in web testing because if a website gets more no of visitors at the same time, the site may become slow, so we need to test if the site can handle more visitors? Is the hardware configuration such as ram and physical hard drive size supports more visitors? How does it handle in the peak hours for banking websites?

Continue lendo

Test plan and Test strategy

Test Strategy:
It is a company level document and developed by QA category people like QA and PM. This document defines "Testing Approach" to achieve testing objective. Test strategy is the freezed part of BRS from which we get Test Policy and Test Strategy.


Components in the Test Strategy are as follows:
1. Scope and objective
2. Business issues
3. Roles and responsibilities
4. Communication and status reporting
5. Test deliverability
6. Test approach
7. Test automation and tools
8. Testing measurements and metrices
9. Risks and mitigation
10. Defect reporting and tracking
11. Change and configuration management
12. Training plan


Test Plan:
Test plan is the freezed document developed from SRS, FS, UC. After completion of testing team formation and risk analysis, Test Lead is preparing test plan document in term of what to test, how to test, who to test, and when to test.
There is one Master Test Plan consists of reviewed Project Test Plan and Phase Test Plan. so there is general talk about Project Test Plan.
Components are as follows:


1. Test Plan id
2. Introduction
3. Test items
4. Features to be tested
5. Features not to be tested
6. Approach
7. Testing tasks
8. Suspension criteria
9. Features pass or fail criteria
10. Test environment (Entry criteria, Exit criteria)
11. Test delivarables
12. Staff and training needs
13. Responsibilities
14. Schedule
15. Risk and mitigation
16. Approach


This is one of the standard approach to prepare test plan document, but things can vary company-to-company...

Continue lendo

Traceability matrix

Traceability matrix is used to map between requirements and test cases it is used to check all requirements are covered or not.


Req id
Req Description
Test case ID
Test conditions
Tester Responsible
Passed/failed status
outstanding defects

Continue lendo

Testing concepts (Severity and priority)

Severity:
seriousness of defect with respect  to functionality

!High:without resolving the defect we r unable to continue testing.
!Medium:compulsory to solve but able to continue !
low:May or may not be resolved.


Prority:Importance of the defect wrt customer (High,medium,low) When we go for examples 1.user interface bugs[low severity]


Eg1:Spelling mistake(High priority) Eg2:Improper allignment(Low priority) 2.Input domain bugs:[medium severity] Eg1:Doesnot allow valid values(high priority) Eg2:allows invalid type also(low priority) 3.Race condition bugs[High severity] Eg1:Deadlock(High priority)


Eg2:improper order or services(Low priority) like this there r many,but the thing is that as the name severity itself says seriousness, based on the seriousness created by the bug we give priority ie., importance

Continue lendo