1. Explain Testing process which is followed in your organization?

Agile methodologies, Sprint model or Scrum model

- Analysis of the requirement

-Test case creation

-Test case review by both (offshore /onshore/client)

-Signoff for the TC

-Control M job execution

-Test Execution

-Results review

-Demo

-Sign off

2. Explain about the Defect lifecycle?

NEW/OPEN/FIXED/CLOSED—if we found any bug in the processing we raise the issue in QC and will
assign it to the concern developer, if the bug was fixed we will reset the application and the affected
components and update / close with comments.

3. Test plan and what are the objects in test plan?

The Objectives / Purpose of testing

WHAT IS IN SCOPE/OUT OF SCOPE

Types of testing ……Functional testing Manual – regression / Automation / Performance / Load etc…

TOOLS REQUIRED/RISKS MTIGATIONS/TEST APPROACH/TEST STRETEGY

Project Milestones :- effort required in days , start date and end date.

4. What is ETL Testing?

ETL testing is for Extract Transform and load.

At the time of transformation, Data are first transformed to staging table (Temporary Table); based on
the business rule the data are mapped into target table , this process is manually mapped / er configure
using ETL tool

Data transformation process speed is based on source and target data ware house.
We need to consider the OLAP(Online Analytic Processing) Structure .Data warehouse Model

Source data consist of (XML,Flat file ,Database.Excel Report.Dataware House

Based on the user requirement, ETL process starts

5. What is Database testing?

Data base testing basically include the following.

1) Data validity testing.
2) Data Integrity testing
3) Performance related to data base.
4) Testing of Procedure, triggers and functions.
For doing data validity testing you should be good in SQL queries
for data integrity testing you should know about referential integrity and different constraint.
For performance related things you should have idea about the table structure and design.
For testing Procedure triggers and functions you should be able to understand the same

In DB testing we need to check for,

1. The field size validation
2. Check constraints.
3. Indexes are done or not (for performance related issues)
4. Stored procedures
5. The field size defined in the application is matching with that in the db.

IT IS MORE LIKE, APPLICATION LAYER TO BACKEND TESTING KIND OF WHAT MANUAL TESTERS DOES
AT BACKEND TO CHECK ALL THE FUNCTIONALITES ARE REFLECTED TO BACKEND

6. Explain about ETL Architecture?

Transactional data from different OLTP systems to

-Landing space (This has more raw data) here it is cleansing and standardized and moved to

-Staging from here using different transformation it moves to

-Data mart and to the DWH (Using query tools and reporting)

7. What are Joins? (Inner Join)

Its also an Equijoin creates new results table by combining column values of two tables (table 1 and
table 2) based upon the join predicate.
8. What are Roles in your project and how do you handled those?

-Analysis of the requirement

-Creating test cases

-Executing the test results.

-Validations as per the requirement.

- Logging of Defects and re testing

9. What is severity and priority? Give examples

Severity : It is term which describe the how the defect is impacting the functionality of the product or
software under test.

we can Severity into several parts depending on the impact of defect on the functionality. most used
Severity types are

1) Blocker : application is not working/ major functionality is completely brown. tester can not do further
testing. tester is blocked.

2) Critical : some part of functionality is brown, tester cannot test some part of functionality and there is
no workaround.

3) Major : in this type, defects are logical defects which does not block any functionality. major type
usually contains functional and major UI defects.

4) Minor : it mostly contains UI defects, minor usability defects. defects which does not harm to
application under test

 Priority :  It is term indicates the importance of the defect and when it should gets addressed or fixed.

Like Severity, Priority also has different types. Priority is defined on the basis of business impact,
development efforts and some other factors.

1) High : it has high business value, end user can not work, unless the defect gets fixed. in this case Priority
should be High, means immediate fix of the defect.

2) Medium: end user can work using workaround but some functionality end user cannot use and that
functionality is not regularly used by the user.

3) Low: no or very less impact on end user

Severity: With respect to the defect that causes impact on the software.

Priority: With respect to the Client needs.

10. Explain the views in SQL..?

A VIEW is a virtual table, through which a selective portion of the data from one or more tables can be

seen. Views do not contain data of their own. They are used to restrict access to the database or to

hide data complexity. A view is stored as a SELECT statement in the database. DML operations on a

view like INSERT, UPDATE, DELETE affects the data in the original table upon which the view is based.

The Syntax to create a sql view is

CREATE VIEW view_name

AS

SELECT column_list

FROM table_name [WHERE condition];

It is the mirror image of table; generally data doesn’t exist

physically in views except materialized view.

11. Difference between drop , delete and Truncate in SQL..?

The DROP command removes a table from the database. All the tables' rows, indexes and privileges will also
be removed. No DML triggers will be fired. The operation cannot be rolled back. - Example

SQL> DROP TABLE emp;

Table dropped.

SQL> SELECT * FROM emp;

SELECT * FROM emp

ERROR at line 1:

ORA-00942: table or view does not exist

The DELETE command is used to remove rows from a table. A WHERE clause can be used to only remove
some rows. If no WHERE condition is specified, all rows will be removed. After performing a DELETE
operation you need to COMMIT or ROLLBACK the transaction to make the change permanent or to undo it.
Note that this operation will cause all DELETE triggers on the table to fire. – Example

SQL> SELECT COUNT(*) FROM emp;

 COUNT(*)

----------

14

SQL> DELETE FROM emp WHERE job = 'CLERK';

4 rows deleted.

SQL> COMMIT;

Commit complete.

SQL> SELECT COUNT(*) FROM emp;

COUNT(*)

----------

TRUNCATE removes all rows from a table. The operation cannot be rolled back and no triggers will be fired.
As such, TRUCATE is faster and doesn't use as much undo space as a DELETE.

SQL> TRUNCATE TABLE emp;

Table truncated.

SQL> SELECT COUNT(*) FROM emp;

COUNT(*)

----------

DROP --DDL COMMAND, (AUTO COMMIT)

DELETE -- DML COMMAND (NEED EXPLICIT COMMIT IS REQUIRED)

12. Different test data preparation techniques..?

One of the most important stages of database testing is preparing of the testing data, because a
clear test data selection is very important in this process. So it’s time to discuss some techniques
of preparing test data. Actually, there are only two of them.
Method 1. Inserting new data
You have to clean the database and then insert all the data as it specified in your test cases. When
all the required data has been inserted, you have to start executing the test cases filling
“Pass/Fail” columns after comparing expected output with the actual one. It could really sound
simple, but it’s not.There are some critical concerns that you have to follow.

 Database empty instance may not be available.

 You may find out that inserted test data is insufficient for testing soma cases such as load
testing and performance.
 Data insertion may become a difficult task due to database table dependencies.
 When you insert limited test data, it may hide some issues, but they could be found by
big data set.
 When inserting data, complex procedures and queries may be required.

The issues, mentioned above are the most important for testing data preparation. But there are
some advantages of this method as well:

 Test cases execution becomes more efficient.

 Bugs isolation doesn’t require any time as the DB is filled only with data specified in the
test cases.
 Testing and results comparison requires less time.
 The test process is clutter-free.

Method 2. Sample data subset is chosen from the actual DB data.

This is more feasible and practical method for preparation of the test data. However this
technique is not for dummies: here you must have some sound technical skills and knowledge in
SQL and DB Schema.
So here you have to copy and then use production data replacing some field values by other
dummy values. This is definitely the best data subset for your test data because it is representing
the production data. But this method is not feasible all the time because of the data security and
some privacy issues.

 We can manually update for whatever scenarios we need to test

in source tables,
 We can copy the data from UAT, if there is no sufficient data in
our source tables.