INTERVIEW QUESTION

Q1. What is the Process for creating a test script?

Step 1 – is to get a thorough understanding of the AUT –
a) This could be by reading the requirement documents thoroughly
b) In absence of docs, we could try to understand the any point of reference that we have – a previous version of the application or wire-frames or screenshots

Step 2 – After understanding the requirements, we make a list of what are the areas in this application that will be have to be tested. In other words, we identify the test requirements. The focus in this step is to identify “What” to test. The outcome of this step is a list of test scenarios.

Step 3 – Once we have the test scenarios, we concentrate next on “How” to test them.  This phase involves writing detailed steps about how to test a particular feature, what data to enter (test data) and what is the expected result.

Once these 3 steps are done, we are ready for testing.

Q2. What are the fields in a bug report?

Following important fields should be included in a good bug report:

A unique ID
Defect description – a short describing what the bug is
Steps to reproduce – details about how to arrive at the error, exact test data, the time at which defect was found(if applicable) environment – any information that will help re-encounter the issue
Module/section of the application (if applicable)
Severity
Screenshot
Responsible QA – in case of any follow up questions regarding this issue

Q3. How to test a customer facing software?

With any application that we test, we are trying to see if a certain set of requirements are met by the application or not.
But when it comes to a user facing site, apart from concentrating on functionality, we also have to look into few the usability features, may be performance and security aspects also to a certain extent.
The first level of testing is – Does the site satisfy its functional requirements.
Example: if it is a loan management site, we need to look at – are the new customer able to apply for a loan,
are the existing customer able to access their loan info, is the interest % applied to the loan amount correct, etc.
The next level of testing is – how easy is it to use the site, do the options make a logical sense and meet the expectations of the user or not.
For example, if the user has to be pass 3-4 screens to submit the basic information they are going to be annoyed, so such issues have to be addressed.
Another example, after entering username and password, the user might click on tab- which means the control should go to “Sign in” button, instead if it’s
going to cancel, the user is going to be really annoyed and the experience of using the site is going to be compromised. Such issues have to be caught.

Performance testing to the complete extent might not be in scope but simple situations like, how long does the search results
take to be displayed and how much time does it take for the system to retrieve a customer info at the peak hour –
these are some example of the kind of things we would want to keep an eye on.

Q4. How to overcome the challenge of not having input documentation for testing?

IF the detailed standard documentation like BRD and FSD are unavailable, the tester will have to depend on some point of reference.
a) Screenshots
b) A previous version of the application
c) Wireframes …etc

Another factor that helps immensely, is to talk to the developers or the business analysts (when available) to get a confirmation on our understanding or clarifications in case of doubts.

When none of these situations work, we can just conceptualize the application based on our previous IT application experience and create the basic set of test scripts. When testing phase comes up, we can set up a portion of test cycle time and do some test case management (make the already created scripts perfect) so we have the doc for the next phases.

Q5. How to get maximum productivity from offshore team?

The key is to make sure that all the testers know about all the modules and that there is no knowledge concentration in one place. Involving everyone in test script peer reviews, defect meetings and KT sessions is going to ensure that everyone is aware of the application to the best extent possible.

Also, by encouraging the concept of team work we can have the team members collaborate, help and aid each other for better productivity.

Regular follow up meetings also help the process very much.

Q6. What are the Roles and Responsibilities of an onsite coordinator? Does he/she test too?

Onsite coordinator is a point of contact for the offshore team and to the client for any information regarding the testing engagement.

This job includes:

KT from and to offshore and clients
Getting the environment to test all ready
Sanity testing, smoke testing
Testing – the key functionality.
Bug review – found by the offshore team
Bug assigning to the respective dev
Presenting metrics
Providing sign off
Yes, even an onsite coordinator has to test.

Q7. Inconsistent bugs – Why onsite can find it but offshore can’t and vice versa – How to handle this situation?

Every bug has to be noted and analyzed – whether it is encountered at onsite or offshore, whether repeatable or not. A real value add to a tester’s job is when we involve ourselves in the Root Cause Analysis process for a bug rather than simply reporting it.

Some of the ways we can handle this situation is:
#1. All the onsite and offshore team members should follow a guideline that screenshots had to be taken for every error that we encounter – repeatable or not

#2. If there are logs, system files or anything like that, that might help us find any evidence of the issue- we should try to find it

#3. Despite all these steps, if we still can’t tell why and when the problem occurs- we should report it to the developer all the same – with as much information as we can.

Q8. Video/audio related testing – What does this include?

How to test an application having video or audio?

Here are the important points to consider:
– Access levels (restricted or not – password controlled)
– Different kinds of environments
– Browser compatibility
– Screen resolutions
– Internet connection speeds
– The specific options on a video – like play, stop, mute etc.
– Video by size
– Response to the videos – comments (limitations on the comment length and number of comments it can take)
– Video responses to the videos
– Interface with social networking sites – interoperability
– Buffering speed
– Embedding the video

Q9. Mobile Application Testing – What does it include briefly?

Mobile App Testing Important Test Scenarios:
– Check if the app works well with multiple carriers and multiple devices
– Usability of the features in a mobile screen
– Testing it in different mobile platforms – like Android and iOS
– Installations, uninstalling, launching the app with network and without network, testing functionality
– Network connections –WiFi, 2G, etc.
– Logs at  iOS iPhone configuration utility  for Android Monitor.bat can be used for debugging



Security – for sites where there is a secure login to access the site, the minimum functionality around it has to be tested. For example, if I leave the site idle for more than 10 minutes, is it auto logging out or not. Something as basic as that should be focused on.

SQL------ Commands And Functions

Comparison Operators

For numbers (INT, DECIMAL, FLOAT), you could use comparison operators: '=' (equal to),
'<>' or '!=' (not equal to), '>' (greater than), '<' (less than), '>=' (greater than or equal to),
'<=' (less than or equal to), to compare two numbers. For example, price > 1.0, quantity
<= 500.
mysql> SELECT name, price FROM products WHERE price < 1.0;
+-----------+-------+
| name | price |
+-----------+-------+
| Pencil 2B | 0.48 |
| Pencil 2H | 0.49 |
+-----------+-------+
2 rows in set (0.00 sec)
mysql> SELECT name, quantity FROM products WHERE quantity <= 2000;
+-----------+----------+
| name | quantity |
+-----------+----------+
| Pen Black | 2000 |
+-----------+----------+
1 row in set (0.00 sec)

String Pattern Matching - LIKE and NOT LIKE

For strings, in addition to full matching using operators like '=' and '<>', we can perform
pattern matching using operator LIKE (or NOT LIKE) with wildcard characters. The wildcard
'_' matches any single character; '%' matches any number of characters (including zero). For
example,
• 'abc%' matches strings beginning with 'abc';
• '%xyz' matches strings ending with 'xyz';
• '%aaa%' matches strings containing 'aaa';
• '___' matches strings containing exactly three characters; and
• 'a_b%' matches strings beginning with 'a', followed by any single character, followed by
'b', followed by zero or more characters.



-- "name" begins with 'PENCIL'
mysql> SELECT name, price FROM products WHERE name LIKE 'PENCIL%';
+-----------+-------+
| name | price |
+-----------+-------+
| Pencil 2B | 0.48 |
| Pencil 2H | 0.49 |
+-----------+-------+
-- "name" begins with 'P', followed by any two characters,
-- followed by space, followed by zero or more characters
mysql> SELECT name, price FROM products WHERE name LIKE 'P__ %';
+-----------+-------+
| name | price |
+-----------+-------+
| Pen Red | 1.23 |
| Pen Blue | 1.25 |
| Pen Black | 1.25|
MySQL also support regular expression matching via the REGEXE operator.

Logical Operators - AND, OR, NOT, XOR

You can combine multiple conditions with boolean operators AND, OR, XOR. You can also invert a
condition using operator NOT. For examples,
mysql> SELECT * FROM products WHERE quantity >= 5000 AND name LIKE 'Pen %';
+-----------+-------------+----------+----------+-------+
| productID | productCode | name | quantity | price |
+-----------+-------------+----------+----------+-------+
| 1001 | PEN | Pen Red | 5000 | 1.23 |
| 1002 | PEN | Pen Blue | 8000 | 1.25 |
+-----------+-------------+----------+----------+-------+
mysql> SELECT * FROM products WHERE quantity >= 5000 AND price < 1.24 AND name
LIKE 'Pen %';
+-----------+-------------+---------+----------+-------+
| productID | productCode | name | quantity | price |
+-----------+-------------+---------+----------+-------+
| 1001 | PEN | Pen Red | 5000 | 1.23 |
+-----------+-------------+---------+----------+-------+
mysql> SELECT * FROM products WHERE NOT (quantity >= 5000 AND name LIKE 'Pen
%');
+-----------+-------------+-----------+----------+-------+
| productID | productCode | name | quantity | price |
+-----------+-------------+-----------+----------+-------+
| 1003 | PEN | Pen Black | 2000 | 1.25 |
| 1004 | PEC | Pencil 2B | 10000 | 0.48 |
| 1005 | PEC | Pencil 2H | 8000 | 0.49 |
+-----------+-------------+-----------+----------+-------+
IN, NOT IN
You can select from members of a set with IN (or NOT IN) operator. This is easier and clearer than
the equivalent AND-OR expression.
mysql> SELECT * FROM products WHERE name IN ('Pen Red', 'Pen Black');
+-----------+-------------+-----------+----------+-------+
| productID | productCode | name | quantity | price |
+-----------+-------------+-----------+----------+-------+
| 1001 | PEN | Pen Red | 5000 | 1.23 |
| 1003 | PEN | Pen Black | 2000 | 1.25 |
+-----------+-------------+-----------+----------+-------+

BETWEEN, NOT BETWEEN

To check if the value is within a range, you could use BETWEEN ... AND ... operator. Again,
this is easier and clearer than the equivalent AND-OR expression.
mysql> SELECT * FROM products
WHERE (price BETWEEN 1.0 AND 2.0) AND (quantity BETWEEN 1000 AND 2000);
+-----------+-------------+-----------+----------+-------+
| productID | productCode | name | quantity | price |
+-----------+-------------+-----------+----------+-------+
| 1003 | PEN | Pen Black | 2000 | 1.25 |
+-----------+-------------+-----------+----------+-------+


ORDER BY Clause

You can order the rows selected using ORDER BY clause, with the following syntax:
SELECT ... FROM tableName
WHERE criteria
ORDER BY columnA ASC|DESC, columnB ASC|DESC, ...
The selected row will be ordered according to the values in columnA, in either ascending (ASC)
(default) or descending (DESC) order. If several rows have the same value in columnA, it will be
ordered according to columnB, and so on. For strings, the ordering could be case-sensitive or caseinsensitive,
depending on the so-called character collating sequence used. For examples,
-- Order the results by price in descending order
mysql> SELECT * FROM products WHERE name LIKE 'Pen %' ORDER BY price DESC;
+-----------+-------------+-----------+----------+-------+
| productID | productCode | name | quantity | price |
+-----------+-------------+-----------+----------+-------+
| 1002 | PEN | Pen Blue | 8000 | 1.25 |
| 1003 | PEN | Pen Black | 2000 | 1.25 |
| 1001 | PEN | Pen Red | 5000 | 1.23 |
+-----------+-------------+-----------+----------+-------+

checklist of Web application testing:

checklist of Web application testing:

1) Functional Testing (Regression, Integration, Smoke Testing)
2) Browser Compatibility Testing
3) Performance Testing
4) Security Testing
5) Production Monitoring
6) Usability Testing


Check links:
Test links to a page from external pages
Test all links on a page for correct operation
Test links to anchors on the same page
Test email mail-to linksIdentify orphan pages - pages that are not linked from other pages


Test Web forms on the page:
Check the field validation logic for each fieldCheck default values for each field
Check that password fields do not show the password contents
Negative test invalid input values for each field
Validate the response to a form submit

Session and Cookie Management Testing:
Check application log-in sessions by enabling and disabling cookies
Negative test cookies by using a mismatching domain
Check that session cookies reset between browser sessions
Check application security by selectively deleting cookies while a test operates

Validate Cascading Style Sheet (CSS) tags:
Identify CSS tags that return 404 or other CSS load errors
Identify HTML id, class, and name attributes that do not match any CSS tags
Validate JavaScript tags:
Identify Script tags that return 404 or other load errors
Identify id, name, on... attributes that do not match any Script tag
Dynamic content testing (aka Database testing):
Check data consistency in database-driven Web forms
Check create, edit, delete, update (CRUD) tasks
Verify data retrieval delivers the correct data
Identify database connectivity and query errors


2) Browser Compatibility Testing:
Differences in Web browsers, operating environments, and hardware devices impact the correct operation of your Web application.
Browser compatibility:

Test your Web application for correct function on several browsers, including Firefox, IE, Chrome, Opera, and Safari. Ideally your Web application handles browser differences elegantly.
Check application function with a variety of browser security profile settings
Verify application function with browser features turned-off (JavaScript, Cookies)
Check browser rendering of your application's user interface
Check the browser's security settings for cross domain access and hacks
Verify consistent application function across multiple versions of a browser
Operating Environment Compatibility:
Check application user interface rendering on OS windowing systems
Check desktop integration functions, including drag-and-drop and file selection
Test your web application on different operating systems, including Windows, Unix, MAC, Linux, and Solaris
Mobile Device Compatibility:
Check application compatibility with device services, including location and dialing services
Check user interface rendering on mobile device screen sizes, including screen rotation


3) Performance Testing:

Web Load Testing
Linear scalability - where an application's performance does not vary as the number of users increases - is the Holy Grail of Web application testing. Load testing identifies a Scalability Index for your Web application performance.
Check server response to browser form submit requests
Identify performance changes over a period of time
Test for functions that stop working at higher levels of user load
Identify the network latency problems on Web application function

Web Stress Testing

Determine how the application responds under high levels of load
Identify portions of the Web application that fail under high levels of load
Identify application function after a system crash or component failure
Identify forms and links that operate differently under high levels of load
Verify correct application operation when device is in and out of range of network services


4) Security Testing:
Protect Web application data and maintain functionality as designed.
Check URLs for operation without loging
Test basic authentication using false user name and password credentials
Check X.509 security certificates on secure Web pages
Test for correct application function upon invalid URL attribute values
Check for application function with invalid input fields, including text fields
Check for Web server protection of inaccessible Web directories or files
Check for Web application identification of security breaches, including error messages and security breach attempts being logged
Test CAPTCHA fields for Web forms and logins
Test browser security settings for moving from secure to insecure pages


5) Production Monitoring
Operate the Web application tests periodically and save the test logs as proof of Servlice Level Agreement (SLA) compliance
Periodically check the end user experience
Provide auto-scaling and load balance systems with end user experience metrics
Check for correct application function from a variety of geographic locations

6) Usability Testing
The design and presentation of an application has a large impact on the success your users will have in using the Web application.
Check for the user to have apparent and easy controls to move from page to page.
Test the flow of a Web application by observing how the user accomplishes their goals
Check that the user can find instructions should they not intuitively know how to operate a function
Test that common navigation objects appear on every page consistently
Test search functions for proper application functions
Content Checking:
Test that content is logically arranged and easy for users to understand
Check for spelling errors
Check that pages adhear to color and pattern style guidelines, including fonts, frames, and borders
Check that images load correctly and with proper sizes

Requirements Traceability Matrix (RTM)

Requirements traceability matrix is a mechanism to track the requirements throughout the project Lifecycle and to make sure that every sure that every requirement is converted into respective test cases.

Requirements Traceability Matrix Development Process:

It is generally used to  allocate a unique identifier  to easily track the requirement  from start to end of the requirement.

Sample  format is :

Why do we need Requirements Traceability Matrix:

RTM  is a powerful tool which helps to identify the inconsistencies between the requirement, project plan and  associated with  product deliveries. Requirements Traceability Matrix serves as a tool to identify Start and End of each requirement and as a result give us an assurance that each agreed or baseline requirement delivered at the end.

Advantage of RTM

• It confirms 100% test coverage
• It highlights any requirements missing or document inconsistencies
• It shows the overall defects or execution status with a focus on business requirements
• It helps in analyzing or estimating the impact on the QA team’s work with respect to revisiting or re-working on the test cases

SQL QUERIES------ INTERVIEW

1. To fetch ALTERNATE records from a table. (EVEN NUMBERED)select * from emp where rowid in (select decode(mod(rownum,2),0,rowid, null) from emp);
2. To select ALTERNATE records from a table. (ODD NUMBERED)select * from emp where rowid in (select decode(mod(rownum,2),0,null ,rowid) from emp);
3. Find the 3rd MAX salary in the emp table.select distinct sal from emp e1 where 3 = (select count(distinct sal) from emp e2 where e1.sal <= e2.sal);
4. Find the 3rd MIN salary in the emp table.select distinct sal from emp e1 where 3 = (select count(distinct sal) from emp e2where e1.sal >= e2.sal);
5. Select FIRST n records from a table.select * from emp where rownum <= &n;
6. Select LAST n records from a tableselect * from emp minus select * from emp where rownum <= (select count(*) - &n from emp);
7. List dept no., Dept name for all the departments in which there are no employees in the department.select * from dept where deptno not in (select deptno from emp);  
   alternate solution:  select * from dept a where not exists (select * from emp b where a.deptno = b.deptno);
   altertnate solution:  select empno,ename,b.deptno,dname from emp a, dept b where a.deptno(+) = b.deptno and empno is null;
8. How to get 3 Max salaries ?select distinct sal from emp a where 3 >= (select count(distinct sal) from emp b where a.sal <= b.sal) order by a.sal desc;
9. How to get 3 Min salaries ?select distinct sal from emp a  where 3 >= (select count(distinct sal) from emp b  where a.sal >= b.sal);
10. How to get nth max salaries ?
    select distinct hiredate from emp a where &n =  (select count(distinct sal) from emp b where a.sal >= b.sal);
11. Select DISTINCT RECORDS from emp table.select * from emp a where  rowid = (select max(rowid) from emp b where  a.empno=b.empno);
12. How to delete duplicate rows in a table?delete from emp a where rowid != (select max(rowid) from emp b where  a.empno=b.empno);
13. Count of number of employees in  department  wise.select count(EMPNO), b.deptno, dname from emp a, dept b  where a.deptno(+)=b.deptno  group by b.deptno,dname;
14.  Suppose there is annual salary information provided by emp table. How to fetch monthly salary of each and every employee?
    select ename,sal/12 as monthlysal from emp;
15. Select all record from emp table where deptno =10 or 40.
    select * from emp where deptno=30 or deptno=10;
16. Select all record from emp table where deptno=30 and sal>1500.
    select * from emp where deptno=30 and sal>1500;
17. Select  all record  from emp where job not in SALESMAN  or CLERK.
    select * from emp where job not in ('SALESMAN','CLERK');
18. Select all record from emp where ename in 'BLAKE','SCOTT','KING'and'FORD'.
    select * from emp where ename in('JONES','BLAKE','SCOTT','KING','FORD');
19. Select all records where ename starts with ‘S’ and its lenth is 6 char.
    select * from emp where ename like'S____';
20. Select all records where ename may be any no of  character but it should end with ‘R’.
    select * from emp where ename like'%R';
21. Count  MGR and their salary in emp table.
    select count(MGR),count(sal) from emp;
22. In emp table add comm+sal as total sal  .
    select ename,(sal+nvl(comm,0)) as totalsal from emp;
23. Select  any salary <3000 emp="" from="" nbsp="" strong="" table.="">
    select * from emp  where sal> any(select sal from emp where sal<3000 p="">
24. Select  all salary <3000 emp="" from="" nbsp="" strong="" table.="">
    select * from emp  where sal> all(select sal from emp where sal<3000 p="">
25. Select all the employee  group by deptno and sal in descending order.
    select ename,deptno,sal from emp order by deptno,sal desc;
26. How can I create an empty table emp1 with same structure as emp?
    Create table emp1 as select * from emp where 1=2;
27. How to retrive record where sal between 1000 to 2000?
    Select * from emp where sal>=1000 And  sal<2000 p="">
28. Select all records where dept no of both emp and dept table matches.
    select * from emp where exists(select * from dept where emp.deptno=dept.deptno)
29. If there are two tables emp1 and emp2, and both have common record. How can I fetch all the recods but common records only once?
    (Select * from emp) Union (Select * from emp1)
30. How to fetch only common records from two tables emp and emp1?
    (Select * from emp) Intersect (Select * from emp1)
31.  How can I retrive all records of emp1 those should not present in emp2?
    (Select * from emp) Minus (Select * from emp1)
32. Count the totalsa  deptno wise where more than 2 employees exist.
    SELECT  deptno, sum(sal) As totalsal
    FROM emp
    GROUP BY deptno
    HAVING COUNT(empno) > 2

TCL Commands----- Transaction Control Language

TCL command is used to manage the transaction in the databases.They are used to manage the changes made by the DML commands.

1. Commit Command

It is used to permanently save any transaction into the databases.

Following is Commit command's syntax,

commit;

2. Rollback Command

This command  restores the databases to the last committed state.

It is also use with savepoint command to jump to a savepoint in a transaction.

Following is Rollback command's syntax,

rollback to savepoint-name;

3. SavePoint Command
SavePoint command is used to temporarily save a transaction so that you can rollback 
to that point whenever necessary.

Following is savepoint command's syntax,

savepoint savepoint-name;

Example of Savepoint and Rollback

Following is the class table,

ID	NAME
1	abhi
2	adam
4	alex

Lets use some SQL queries on the above table and see the results.

INSERT into class values(5,'Rahul');
commit;
UPDATE class set name='abhijit' where id='5';
savepoint A;
INSERT into class values(6,'Chris');
savepoint B;
INSERT into class values(7,'Bravo');
savepoint C;
SELECT * from class;

The resultant table will look like,

ID	NAME
1	abhi
2	adam
4	alex
5	abhijit
6	chris
7	bravo

Now rollback to savepoint B

rollback to B;
SELECT * from class;

The resultant table will look like

ID	NAME
1	abhi
2	adam
4	alex
5	abhijit
6	chris

Now rollback to savepoint A

rollback to A;
SELECT * from class;

The result table will look like

ID	NAME
1	abhi
2	adam
4	alex
5	abhijit

E-R Diagram

ER-Diagram is a visual representation of data that describes how data is related to each other

Components of E-R Diagram

1. Entity:  Entity refers to a real world object that might depict a table in an SQL Server database. Databases are often constructed in the basis of an Entity-relationship diagram.

2.Weak Entity : In a relational database, weak entity  is a entity that cannot be uniquely identified by its attributes, it should take the help  of foreign key in conjunction with its attributes to create a primary key.

3. Attribute: It defines the properties of the table.or example, Name, Age, Address etc can be attributes of a Student.

4. Key Attribute: It represents  the primary key in a particular entity/element

For example, id in the student entity type.

5. Non-Key Attribute: These are the attributes other than candidate key  in a given table.For example in Name, First Name is non-Key Attribute which does not have the main characteristics of the entity.

6. Composite Attribute: In this type, all the attributes are arranged in a tree-structured way and every node is connected to its attribute.

Relationship:

It describes the bond  between the entities.

There are generally three types of relationships:

1. Binary relationship

2. Recursive Relationship

3. Ternary Relationship

BINARY RELATIONSHIP

Binary Relationship means relation between two Entities. This is further divided into three types.

1. One to One : This type of relationship is rarely seen in real world.

2. One to Many : It reflects business rule that one entity is associated with many number of same entity. The example for this relation might sound a little weird, but this means that one student can enroll to many courses, but one course will have one Student.

Many to One : It reflects business rule that many entities can be associated with just one entity. For example, Student enrolls for only one Course but a Course can have many Students.

RECURSIVE RELATIONSHIP

When an Entity is related with itself it is known as Recursive Relationship.

TERNARY RELATIONSHIP

Relationship of degree three is called Ternary relationship.