To DROP A COLUMN in an existing table, the Oracle ALTER TABLE syntax is:
ALTER TABLE table_name DROP COLUMN column_name;
Let’s look at an example that shows how to drop a column in an Oracle table using the ALTER TABLE statement.
For example:
ALTER TABLE customers DROP COLUMN customer_name;
This Oracle ALTER TABLE example will drop the column called customer_name from the table called customers.
Wait Statement is used in selenium to make some delay and during that period of time we need to do something and or to wait for presence of element.We can make wait a website three types Implicit wait Explicit wait and Fluent Wait.All the waits statement are different function and different uses.
Normal Wait-Thread .sleep(millisecond) // It is also known as hard coded wait this wait statement will wait for a particular period of time.
This wait statement is not used in selenium script because of the element is displayed in the short duration of time it will wait unnecessary for rest of the time. 
syntax-driver.manage.timeout.implicitlywait(second,Timeunit.SECOND).
Implicitly wait will monitor the entire html source code and it will wait till page is loaded.Once the page is loaded within short duration of time it will not wait for rest of the time.And it will pass the control to the next line,But this implicit wait will not wait for ajax application.
It is used before get method .Before throwing page load timeout expectation.It will wait for page to load.If the page is not loaded in that duration of time it will throw expectation in the console,
WebDriverWait wait=new WebDriverWait(driver,20);
wait.until(ExpectedCondition.presenseofElementLocated(By.XPATH(“”)));
Explicit wait will wait for element to be present to be present on the user interface.It will check after every 500 millisecond.If the element is present on the user interface pass the control to next line .Example Link
Implicit and Explicitly wait is also known as synchronization.
Another type of wait is FluentWait which is used to check the element is present or not dynamically at each polling interval with a timeout constraints.Example Link
For reading files from the .xlsx file we need the following .jar files to be imported to the Build Path.Downloads the followings and import the version.
poi-ooxml-3.11-beta2.jar
poi-ooxml-schemas-3.11-beta2.jar
xmlbeans-2.6.0.jar
stax-api-1.0.1.jar
If you are not using Maven then add following JAR files in your
poi-3.11-beta2.jar
commons-codec-1.9.jar
poi-ooxml-3.11-beta2.jar
poi-ooxml-schemas-3.11-beta2.jar
xmlbeans-2.6.0.jar
stax-api-1.0.1.jar
Along with the l2wish.xlsx file.
Set the location of file in accordance to your system.
Along with the following dependency as in my pom.xml .This pom.xml files i was created for my project i am posting my code bellow.
Main program file contains the following code
package test3;
import java.io.FileInputStream;
import org.apache.poi.ss.usermodel.Row;
import org.apache.poi.ss.usermodel.Sheet;
import org.apache.poi.xssf.usermodel.XSSFWorkbook;
import org.testng.annotations.DataProvider;
import org.testng.annotations.Test;
import test1.ExcelHelper;
public class MyClass {
Object[][] obb;
ExcelHelper Excelelperpag = new ExcelHelper();
@Test(dataProvider = "getexcel")
public void pro(String uname, String pwd) {
System.out.println(uname);
System.out.println(pwd);
}
@DataProvider()
public Object[][] getexcel() {
FileInputStream fis;
try {
fis = new FileInputStream("D:\\l2wish.xlsx");
XSSFWorkbook wb = new XSSFWorkbook(fis);
Sheet sh = wb.getSheet("Sheet1");
int count = sh.getLastRowNum();
System.out.println("Count=" + count);
obb = new Object[count][2];
for (int i = 0; i < count; i++) {
Row rw = sh.getRow(i);
obb[i][0] = rw.getCell(0).getStringCellValue();
obb[i][1] = rw.getCell(1).getStringCellValue();
}
} catch (Exception e) {
e.printStackTrace();
}
return obb;
}
}
POM.XML
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>test2</groupId> <artifactId>test3</artifactId> <version>0.0.1-SNAPSHOT</version> <dependencies> <dependency> <groupId>org.seleniumhq.selenium</groupId> <artifactId>selenium-java</artifactId> <version>3.0.1</version> </dependency> <dependency> <groupId>org.testng</groupId> <artifactId>testng</artifactId> <version>6.8</version> <scope>test</scope> </dependency> <dependency> <groupId>org.apache.poi</groupId> <artifactId>poi</artifactId> <version>3.11-beta2</version> </dependency> <dependency> <groupId>org.apache.poi</groupId> <artifactId>poi-ooxml</artifactId> <version>3.9</version> </dependency> <dependency> <groupId>org.apache.maven.surefire</groupId> <artifactId>surefire</artifactId> <version>2.19.1</version> <type>pom</type> </dependency> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>1.2.17</version> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.19.1</version> <configuration> <suiteXmlFiles> <suiteXmlFile>testng.xml</suiteXmlFile> </suiteXmlFiles> </configuration> </plugin> </plugins> </build> </project>
| Command | Description |
| cat [filename] | Display file’s contents to the standard output device (usually your monitor). |
| cd /directorypath | Change to directory. |
| chmod [options] mode filename | Change a file’s permissions. |
| chown [options] filename | Change who owns a file. |
| clear | Clear a command line screen/window for a fresh start. |
| cp [options] source destination | Copy files and directories. |
| date [options] | Display or set the system date and time. |
| df [options] | Display used and available disk space. |
| du [options] | Show how much space each file takes up. |
| file [options] filename | Determine what type of data is within a file. |
| find [pathname] [expression] | Search for files matching a provided pattern. |
| grep [options] pattern [filesname] | Search files or output for a particular pattern. |
| kill [options] pid | Stop a process. If the process refuses to stop, use kill -9 pid. |
| less [options] [filename] | View the contents of a file one page at a time. |
| ln [options] source [destination] | Create a shortcut. |
| locate filename | Search a copy of your filesystem for the specified filename. |
| lpr [options] | Send a print job. |
| ls [options] | List directory contents. |
| man [command] | Display the help information for the specified command. |
| mkdir [options] directory | Create a new directory. |
| mv [options] source destination | Rename or move file(s) or directories. |
| passwd [name [password]] | Change the password or allow (for the system administrator) to change any password. |
| ps [options] | Display a snapshot of the currently running processes. |
| pwd | Display the pathname for the current directory. |
| rm [options] directory | Remove (delete) file(s) and/or directories. |
| rmdir [options] directory | Delete empty directories. |
| ssh [options] user@machine | Remotely log in to another Linux machine, over the network. Leave an ssh session by typing exit. |
| su [options] [user [arguments]] | Switch to another user account. |
| tail [options] [filename] | Display the last n lines of a file (the default is 10). |
| tar [options] filename | Store and extract files from a tarfile (.tar) or tarball (.tar.gz or .tgz). |
| top | Displays the resources being used on your system. Press q to exit. |
| touch filename | Create an empty file with the specified name. |
| who [options] | Display who is logged on. |
| The root Account in Ubuntu is disabled by default because his password is not set. But if you’d like to use root Account by some reason, it’s possible to use like follows. | |
| [1] | The user account added during installation is set an administrative account with Sudo, so it’s easy to get root account’s shell like follows. |
| xerus@dlp:~$
sudo -s [sudo] password for xerus: # own password root@dlp:~# # switched |
| [2] | Or it’s possible to switch to root account with su command to set root account’s password. |
| xerus@dlp:~$
[sudo] password for xerus: # own password Enter new UNIX password: # set root password Retype new UNIX password: # confirm passwd: password updated successfully xerus@dlp:~$ su – Password: # input root password root@dlp:~# # switched |
| * | The examples on this site shows as a root account. If you use Sudo, add “sudo” on the head of commands.
It had better to limit user if you enable root account. |
| [3] | For limit to do su command, set like follows. |
| root@dlp:~#
vi /etc/pam.d/su # line 15: uncomment and add a group which is allow to do su command auth required pam_wheel.so group=adm |
Run the following command in the terminal:
123sudo apt-get install mysql-serversudo apt-get install mysql-clientsudo apt-get install libmysql-java
This will install both in the most up to date version within your repositories. You will be prompted for a root password. You then need to login and setup the server. To do that, run the following command:
1mysql -u root -p
Password will be asked and after that you will be connected to the server. You have to create a database to work on. Run the following command to create one:
1CREATE [database_name];
Replace [database_name] with the name you want. Now, we have to switch database. Run following command in the terminal:
1>USE [database_name];
Now, we have to set classpath. Enter this command at the end of you bashrc file:
1export CLASSPATH=$CLASSPATH:/usr/share/java/mysql-connector-java.jar
In you favorite IDE, go to Project Properties tab, and click “Add External Jars”. Choose the jar file located at “/usr/share/java/” directory, in this case “mysql-connector-java.java”. Now test this connection using this program:
import java.sql.Connection;import java.sql.DriverManager; class JDBCTest { String url = “jdbc:mysql://localhost”; String user = “username”; String password = “password”; public static void main(String args[]) { try { Connection con; con = DriverManager.getConnection(url, user, password); System.out.println(“Success”); } catch (Exception e) { e.printStackTrace(); } }}
After running this program, “Success” message will be shown if the connection is sucessful.
Got problems? Let me know in the comments.v
1.Can u let me know the example of some defect that was identified in your project?
A-
-Before that i found in payment option of menu items not showing recently updated payment.
-I also detected some specific windows are making delay in opening for intraday chart with smaller time frame.
2.What is severity?
A-Severity is the impact of defect on the customer business application.
2.1.High severity and high priority bug?
A-When a banking website is not showing the balance of an customer is an high priority and high severity bug.
2.2.High severity and low priority bug?
A-When we are generating the yearly statement of current year its showing error.
or Customer is not able to purchase product by using old browser.
2.3.Low severity and high priority bug?
A-Spelling mistake on home page
or Company logo is not displaying.
2.4 Different types of severity?
A-
Critical-The defect affects critical functionality or critical data. It does not have a workaround. Example: Unsuccessful installation, complete failure of a feature.
Blocker-The defect affects major functionality or major data. It has a workaround but is not obvious and is difficult. Example: A feature is not functional from one module but the task is doable if 10 complicated indirect steps are followed in another module/s.
Minor: The defect affects minor functionality or non-critical data. It has an easy workaround. Example: A minor feature that is not functional in one module but the same task is easily doable from another module.
Trivial: The defect does not affect functionality or data. It does not even need a workaround. It does not impact productivity or efficiency. It is merely an inconvenience. Example: Petty layout discrepancies, spelling/grammatical errors.
2.4.Low severity and low priority?
A-Terms and condition page is taking too much time to loading.
3.Who sets the severity in your project?
A-This is set by project manager or product manager.
4.What is priority?
A-Priority is the measure of urgency attached to fixing a defect.
4.1.Different types of priority?
A-
5.Who sets the priority in your project.
A-Developer and Project Manger set priority.
6.What is SDLC?
A- A framework to define each and every steps to be carried out during a software development is called as SDLC?
7.What are the different types of SDLC model?
A-Water Fall
Prototype
Spiral
V
Hybrid(Spiral & Prototype)
(V & Prototype)
8.What are the advantages and disadvantages of SDLC model?
A-Advantages-
-Formal Review at end of the each stage is very suitable for managerial control.
-Throughout the life cycle it followed by systematic documentation.
-The complete cycle goes thorough intermediate stages that can be reviewed to verify weather project is going as per the client needs and requirement.If not they can modify the project as per their requirement at very initial stage of project.
Disadvantages-
-Major problem can not identified from end user prospective unless until the product is fully developed.
-Major challenged can not properly specified in side SRS document as user expected.
-User can not immediate verify the intermediate products and give review this product is suitable for his requirement or not?
-Another disadvantage of a program or software that follows the SDLC program is it encourages stiff implementation instead of creativity. There are requirements that must be met and that is all that developers complete.
-It is difficult to write the documentation part a lots of efforts required to maintain correctly the documentation.
9.Can you explain the V model and Agalie model?
A-V model is the enhance version of waterfall model.It allow us to verify and validate the project at each and every stages of development.
10.In your current project which model you having followed?
While explaining use the word we.
A-We used to follows V and Spiral Model in our project.
11.Who decide this model should followed in your project.
A-Project manager and system analyst team used to decide which model should followed.
12.Why did you select this model for your project?
A-This model is best suitable for our our client,Also it best suites for the project where requirements are not complete and client is new to domain.
13.What is software testing?
A-It is the process by ensuring are we building the right product!
14.Why the software need to be tested?
A-Whether this software meets with the client requirement or not and also have we made done the procut right which meets the client expectation!
15.What are different types of software testing?
A-Black box testing
White Bot Testing
Grey Testing
16.What are different labels of software testing?
A-
17.Why did you chose your carrier in software testing?
A-I like to handle risk,The testing process involve risk and also creativity thinking,So i decide to get into this filed.
18.What is white box testing?
A-The testing done by the developer during the development is known as white box testing.
19.Different types of white box testing?
A-1.Clear Box Testing
2.Open Box Testing
3.Logic Driven Testing
4.Path Driven Testing
5.Structural Testing
20.Who dose white box testing?
A-Developers do the white box testing.
21.Who did the white box testing in your current project?
A-Development team did the white-box testing.
22.When did they do the white box testing in current project?
23.How did they do white box testing in your current project?
A-Every Friday night they run the unit test suite on the new build and if the major of the test are passed then then they give the new build to the testing team on Monday morning.
24.What is black box testing?
We used to test the functionality of the software rather than looking the internal code structure is known as black box testing.
25.What is the difference between white box testing and black box testing?
a.White box focus on the internal structure of the code where as black box focus on functionality of the code form out side whether it meets the user requirement.
b.In white-box program logic is tested where in black box we do not concern about the logic.
c.White box is a structure and design based testing where as black box specification based testing.
26.What is functional testing?
A-Functional testing is the testing which is performed to verify that the software is functioning accordance with the design specification.During the functionality testing we check the application functions,test inputs,menu functions,transaction functions,database updates etc.
27.Can u explain how you have done functional testing in your current project?
28.What is integration testing?
A-Testing the data flow between two different module or two different fetchers is known as integration testing.
29.Why do we do Integration Testing?
A-We do integration testing to check the interfaces are working correctly or not.
30.Different types of Integration Testing?
A-a.Incremental Integration Testing.
b.Non incremental integration testing.
31.When 1 module is build and other module is yet to build what will be the test approach?
A-We use a dummy module known as stubs or driver.
32.What are stubs and driver?
A-Stubs-When the child module is not yet developed replaced by a dummy module is known as stubs.
Driver-When we do integration testing,We use a dummy parent module instead of parent module is known as driver.
33.In your current project can you explain how you have done Integration Testing?
A-Ans should be starts with we have.
34.What is system testing?
35.What is difference between system testing and end to end testing?
A-
36.Can u explain how you have done system testing in your current project?
37.Who is involved in the installation of the build in testing environment?
A-We had a dedicated team called release engineer or build engineer who was taking care of the code and setting of the testing environment wherein i have not involved in the installation of the build in the testing environment in my project.
38.What is smoke testing?
A-We used to do smoke testing to ensure that whether the build is ready for testing or not.
39.When do we do smoke testing?
A-We used to do smoke test before any testing at first when a new build is lunched.
40.Why does the test engineer do smoke testing?
A-We used to do smoke test to ensure the current build is testable or not?
Smoke testing is conducted to ensure whether the most crucial functions of a program are working, but not bothering with finer details. (Such as build verification.
41.What is the difference between smoke and sanity testing?
SMOKE TESTING:
SANITY TESTING:
42.Can u explain how how do you have done smoke testing in your current project?
43.What is ad-hoc testing?
A-The very term ad-hoc implies the lack of structure or something that is not methodical. When you talk about ad-hoc testing, it means that it is a form of black box or behavioral testing performed without any formal process in place.
The formal process here means having the documentation like requirement documents, test plan, test cases and proper test planning in terms of its schedule and order of performed tests. Also any actions performed during the testing are not typically documented.
44.Why we do the ad-hoc testing?
A-
45.At which stage we do ad hoc testing?
A-
46.Can u explain how you have done the ad-hoc testing in the current project?
47.What is release?
48.When to start system testing?
49.When to stop system testing?
a) When all the requirements are adequately executed successfully through test
cases
b) Bug reporting rate reaches a particular limit
c) The test environment no more exists for conducting testing
d) The scheduled time for testing is over
e) The budget allocation for testing is over]
50.What is compatibility testing?
51.What are the defect was identified during the compatibility testing?
52.When we do compatibility testing?
53.Which platform have you done the compatibility testing?
54.How do you decide the platform?
55.What is functionality issue and compatibility issue?
56.What is exploratory testing?
57.When we do the exploratory testing?
58.Have you ever done the exploratory testing in your current project?
59.Why do we do exploratory testing?
60.What are the drawbacks when we do the exploratory testing?
61.What is reliability testing?
62.What is usability testing?
63.What kind of application we do usability testing?
64.What are the different check point or checklist you might you might look when doing the reliability testing?
65.What is regression testing?
66.Different types of regression testing?
67.How do you find or identified the impact area in your project?
68.When we go for the fully regression testing?
69.Can you explain who how you have done the regression testing in your current project?
70.Drawbacks of regression testing?
71.When do we go for automation?
72.Explain STLC in detail?
73.What is difference between regression testing and retesting?
74.In your current project what is the process or approach you followed to test the project?
75.Difference between SDLC and STLC.
76.What is traceability matrix?
77.Can you write the traceability template that you have followed in your project?
78.Advantages of traceability matrix ?
79.Can you write the traceability template followed in project?
80.Advantages of traceability matrix?
81.What is retrospective meeting?
82.Who are the people who are involved in retrospective meeting?
84.What is test plan?
85.Who prepare test plan in your project?
86.What is the objective of preparing test plan in project?
87.What is the difference between test plan and test case?
88.What are context of test plan?
89.How will you define which feature are they are they going to test in your current project?
90.When to stop testing?
91.What are deliverable?
92.Can you explain the roles and responsibility in your current project?
93.What is defect life-cycle?
94.What is the difference between test approach and test methodology?
95.What is performance testing?
96.What are difference types of performance testing?
97.What is non functional testing?
98.What is the difference between functional and non functional testing?
99.What is test case?
100.Why do we write the test case?
101.Where do we write test case?
102.Can u explain the steps to write the test case?
103.Can u write a test case temple that you have been followed in your project?
104.Is testing constructive or destructive?
105.What is the difference between testing and quality?
106.Why does the software has a defect?
107.If you can not deliver a defect free of software what is use of testing?
108.What are the attribute of a good test engineer?
A-Good in observation
-Good in communication skill
-Should test the application from end user perspective.
109.What is big bang testing?
110.What is component testing?
111.What is positive testing?
112.What is -ve testing?
113.Can we conduct system testing directly by avoiding the functional and integration testing?
114.What are types of acceptance testing?
115.What is your involvement in acceptance testing?
116.Enplane test case design technique ?
117.How do u identify the smoke test?
118.After receiving the build what will you do?
119.Until smoke test pass what will the rest of the team will do?
120.Do you report the defect smoke testing is failed?
121.Who identifies the regression test suites?
122.What is difference between testing technique and testing types?
123.What is review?
124.Explain the review process that you have followed in your project?
125.How do you decide the review documentation?
126.What is code review?
127.What is difference between static and dynamic testing?
128.How you will receive the project requirement?
129.Is the testing team involved in the SRS preparation?
130.What is the difference between verification and validation?
131.After understanding the requirement what will you do?
132.Should you understand the whole project functionality or only the functionality assigned to you?
133.What is use cases?
134.What is user stories?
135.Explain the various test that was conducted in your project?
136.How many types of test plan are their?
137.Do you have any white box experience in your current project?
138.What are different categories of testing?
139.What are different categories of black box design technique?
140.What are VBA?
141.What is EP?
142.Explain how do you test the following?
Mobile,Ac,Elevator,Water Bottle,Pen,Tv,Traffic Signal?
143.What are the different categories of white box testing?
144.What are the filed in the test case?
145.What a test scenario?
A-It is nothing but the functional scenarios for which the testing has to be conducted is also called as test condition.
146.What is most difficult part of test design?
147.How may test case you can write per day,& till now how many you have written?
148.What is the next procedure you follow after writing the test case?
149.How do you know that test case are completed or not?
150.How do u design the test case whose requirements are frequently changing?
151.I want to design the test case for a new domain in which you have not worked before do you think you can handle this?
152.Explain the scenario where you are not able to write the test case for given requirement?
153.What is the % of +ve and -ve test have you written in your project?
A: +ve = 60%
-ve = 40%
154.How frequently the build is release and how do you know the build is ready for testing?
155.Whome do you _______________________
156.What will you do if the test case are failed?
157.In the module you check out are their are any issue or defect was they identifay after the realese?
158.What information do you provide with the defect?
159.Do you run the agression test for every defect fixed?
160.How you will you handle a developer who is not aggreing the defect you have reported is validate?
161.How do you handle the aggresive developer?
162.you are repening the defect fixed by developer how do ypou handle this situation?
163.Explain the hot technical discussion that you adding development in your project?
164.Who take decission when to stop testing?
165.What is impact analysis?
166.What if we dont find solution for the critical defect will you stop it?
167.Who allocate the work in you r project?
168.Explain the various situation that you are faced during the testing?
169.How do you report your manager on dailly basic?
170.What is the difference between testing and debugging?
171.Which is a defect tracking tool you have includes in current project?
172.Write the defect report?
173.Write the defect report in you r project?
174.Which is important money or work?
A-Work is imporatant but in this age money also more importatnt.
175.What are key challanges of software testing?
A-Appalication should be stable.
-Understanding the requirment>
-Testing always iunder the time constraints.
-Which test to execute first.
-Testing the complete applaication.
-Domain knowledge and the business user perspective.
-Frequently changing the requirment.
-Reggression testing.
-Lack of skilled tester.
176.What is conformation testing?
A-It is also called as regresion testing.
177.What is exclusive testing?
A-It means that testing each and component in application with every possible number of input.
Note-Asper Principle of software testing principle exclusive testing is impossible,bcoz it require more time and which might delay in release application.
178. What is a test strategy?
Answer:
A test strategy must address the risks and present a process that can reduce those
risks.
The two components of Test strategy are:
a) Test Factor: The risk of issue that needs to be addressed as a part of the test
strategy. Factors that are to be addressed in testing a specific application
system will form the test factor.
b) Test phase: The phase of the systems development life cycle in which testing
will occur.
IEEE 829-2008, also known as the 829 Standard for Software Test Documentation, is an IEEE standard that specifies the form of a set of documents for use in defined stages of software testing, each stage potentially producing its own separate type of document.
1. Test plan identifier
2. Introduction
3. Test items
4. Features to be tested
5. Features not to be tested
6. Approach
7. Item pass/fail criteria
8. Suspension criteria and resumption requirements
9. Test deliverables
10. Testing tasks
11. Environmental needs
12. Responsibilities
13. Staffing and training needs
14. Schedule
15. Risks and contingencies
16. Approvals
Its a Index of Test plan only.
Each point will help you to elaborate your test plan step by step.
Take this as a guideline and develop a full Test plan for Your project.
Table of Contents :
1. Introduction
1.1. Test Plan Objectives
2. Scope
2.1. Data Entry
2.2. Reports File Transfer
2.3. File Transfer
2.4. Security
3. Test Strategy
3.1. System Test
3.2. Performance Test
3.3. Security Test
3.4. Automated Test
3.5. Stress and Volume Test
3.6. Recovery Test
3.7. Documentation Test
3.8. Beta Test
3.9. User Acceptance Test
4. Environment Requirements
4.1. Data Entry workstations
4.2 MainFrame
5. Test Schedule
6. Control Procedures
6.1 Reviews
6.2 Bug Review meetings
6.3 Change Request
6.4 Defect Reporting
7. Functions To Be Tested
8. Resources and Responsibilities
8.1. Resources
8.2. Responsibilities
9. Deliverables
10. Suspension / Exit Criteria
11. Resumption Criteria
Test Plan Template:
(Name of the Product)
Prepared by:
(Names of Preparers)
(Date)
TABLE OF CONTENTS
1.0 INTRODUCTION
2.0 OBJECTIVES AND TASKS
2.1 Objectives
2.2 Tasks
3.0 SCOPE
4.0 Testing Strategy
4.1 Alpha Testing (Unit Testing)
4.2 System and Integration Testing
4.3 Performance and Stress Testing
4.4 User Acceptance Testing
4.5 Batch Testing
4.6 Automated Regression Testing
4.7 Beta Testing
5.0 Hardware Requirements
6.0 Environment Requirements
6.1 Main Frame
6.2 Workstation
7.0 Test Schedule
8.0 Control Procedures
9.0 Features to Be Tested
10.0 Features Not to Be Tested
11.0 Resources/Roles & Responsibilities
12.0 Schedules
13.0 Significantly Impacted Departments (SIDs)
14.0 Dependencies
15.0 Risks/Assumptions
16.0 Tools
17.0 Approvals
1.0 INTRODUCTION
A brief summary of the product being tested. Outline all the functions at a high level.
2.0 OBJECTIVES AND TASKS
2.1 Objectives
Describe the objectives supported by the Master Test Plan, eg., defining tasks and responsibilities, vehicle for communication, document to be used as a service level agreement, etc.
2.2 Tasks
List all tasks identified by this Test Plan, i.e., testing, post-testing, problem reporting, etc.
3.0 SCOPE
General
This section describes what is being tested, such as all the functions of a specific product, its existing interfaces, integration of all functions.
Tactics
List here how you will accomplish the items that you have listed in the “Scope” section. For example, if you have mentioned that you will be testing the existing interfaces, what would be the procedures you would follow to notify the key people to represent their respective areas, as well as allotting time in their schedule for assisting you in accomplishing your activity?
4.0 TESTING STRATEGY
Describe the overall approach to testing. For each major group of features or feature combinations, specify the approach which will ensure that these feature groups are adequately tested. Specify the major activities, techniques, and tools which are used to test the designated groups of features.
The approach should be described in sufficient detail to permit identification of the major testing tasks and estimation of the time required to do each one.
4.1 Unit Testing
Definition:
Specify the minimum degree of comprehensiveness desired. Identify the techniques which will be used to judge the comprehensiveness of the testing effort (for example, determining which statements have been executed at least once). Specify any additional completion criteria (for example, error frequency). The techniques to be used to trace requirements should be specified.
Participants:
List the names of individuals/departments who would be responsible for Unit Testing.
Methodology:
Describe how unit testing will be conducted. Who will write the test scripts for the unit testing, what would be the sequence of events of Unit Testing and how will the testing activity take place?
4.2 System and Integration Testing
Definition:
List what is your understanding of System and Integration Testing for your project.
Participants:
Who will be conducting System and Integration Testing on your project? List the individuals that will be responsible for this activity.
Methodology:
Describe how System & Integration testing will be conducted. Who will write the test scripts for the unit testing, what would be sequence of events of System & Integration Testing, and how will the testing activity take place?
4.3 Performance and Stress Testing
Definition:
List what is your understanding of Stress Testing for your project.
Participants:
Who will be conducting Stress Testing on your project? List the individuals that will be responsible for this activity.
Methodology:
Describe how Performance & Stress testing will be conducted. Who will write the test scripts for the testing, what would be sequence of events of Performance & Stress Testing, and how will the testing activity take place?
4.4 User Acceptance Testing
Definition:
The purpose of acceptance test is to confirm that the system is ready for operational use. During acceptance test, end-users (customers) of the system compare the system to its initial requirements.
————
Participants:
Who will be responsible for User Acceptance Testing? List the individuals’ names and responsibility.
Methodology:
Describe how the User Acceptance testing will be conducted. Who will write the test scripts for the testing, what would be sequence of events of User Acceptance Testing, and how will the testing activity take place?
4.5 Batch Testing
4.6 Automated Regression Testing
Definition:
Regression testing is the selective retesting of a system or component to verify that modifications have not caused unintended effects and that the system or component still works as specified in the requirements.
Participants:
Methodology:
4.7 Beta Testing
Participants:
Methodology:
5.0 HARDWARE REQUIREMENTS
Computers
Modems
6.0 ENVIRONMENT REQUIREMENTS
6.1 Main Frame
Specify both the necessary and desired properties of the test environment. The specification should contain the physical characteristics of the facilities, including the hardware, the communications and system software, the mode of usage (for example, stand-alone), and any other software or supplies needed to support the test. Also specify the level of security which must be provided for the test facility, system software, and proprietary components such as software, data, and hardware.
Identify special test tools needed. Identify any other testing needs (for example, publications or office space). Identify the source of all needs which are not currently available to your group.
6.2 Workstation
7.0 TEST SCHEDULE
Include test milestones identified in the Software Project Schedule as well as all item transmittal events.
Define any additional test milestones needed. Estimate the time required to do each testing task. Specify the schedule for each testing task and test milestone. For each testing resource (that is, facilities, tools, and staff), specify its periods of use.
8.0 CONTROL PROCEDURES
Problem Reporting
Document the procedures to follow when an incident is encountered during the testing process. If a standard form is going to be used, attach a blank copy as an “Appendix” to the Test Plan. In the event you are using an automated incident logging system, write those procedures in this section.
Change Requests
Document the process of modifications to the software. Identify who will sign off on the changes and what would be the criteria for including the changes to the current product. If the changes will affect existing programs, these modules need to be identified.
9.0 FEATURES TO BE TESTED
Identify all software features and combinations of software features that will be tested.
10.0 FEATURES NOT TO BE TESTED
Identify all features and significant combinations of features which will not be tested and the reasons.
11.0 RESOURCES/ROLES & RESPONSIBILITIES
Specify the staff members who are involved in the test project and what their roles are going to be (for example, Mary Brown (User) compile Test Cases for Acceptance Testing). Identify groups responsible for managing, designing, preparing, executing, and resolving the test activities as well as related issues. Also identify groups responsible for providing the test environment. These groups may include developers, testers, operations staff, testing services, etc.
12.0 SCHEDULES
Major Deliverables
Identify the deliverable documents. You can list the following documents:
– Test Plan
– Test Cases
– Test Incident Reports
– Test Summary Reports
13.0 SIGNIFICANTLY IMPACTED DEPARTMENTS (SIDs)
Department/Business Area Bus. Manager Tester(s)
14.0 DEPENDENCIES
Identify significant constraints on testing, such as test-item availability, testing-resource availability, and deadlines.
15.0 RISKS/ASSUMPTIONS
Identify the high-risk assumptions of the test plan. Specify contingency plans for each (for example, delay in delivery of test items might require increased night shift scheduling to meet the delivery date).
16.0 TOOLS
List the Automation tools you are going to use. List also the Bug tracking tool here.
17.0 APPROVALS
Specify the names and titles of all persons who must approve this plan. Provide space for the signatures and dates.
Name (In Capital Letters) Signature Date
1.
2.
3.
4.
You can also Download this Sample Test p
To DROP A COLUMN in an existing table, the Oracle ALTER TABLE syntax is:
ALTER TABLE table_name DROP COLUMN column_name;
Let’s look at an example that shows how to drop a column in an Oracle table using the ALTER TABLE statement.
For example:
ALTER TABLE customers DROP COLUMN customer_name;
This Oracle ALTER TABLE example will drop the column called customer_name from the table called customers.
CategoriesMySql, Oracle
This command is used to alter table existing data type.By giving this command we can change the parameter of an table.
ALTER TABLE table_name MODIFY column_name column_type;
alter table emp modify id number(20);
Alter table command is used to modify the table structure we can add a column or modify column.
Syntax
ALTER TABLE table_name
ADD column_name datatype
eg-alter table test add mobile number(10);
Modifying a column
Syntax
ALTER TABLE “table_name”
RENAME COLUMN “column 1” TO “column 2”;
In order to overcome the drawbacks of waterfall model,Spiral Model,Prototype Model also if the requirements are not verified then we go V-Model
Note-This model is best suitable for verification and validation
Unit Testing-Testing each and every lines in the source code.
Functional Testing-Testing the entire functionality of an application against the requirement specification.
Integration testing – Testing the data flow between two module.
System testings – End to end testing done by the test engineer.
Acceptance testings – End to end testing done by customer.
As soon as customer gives a requirement to the business analyst the requirement will be re-viewed by customer at the very initial stage to avoid Conflict requirement,Wrong requirement,Missing requirement
Conflict Requirement -In the CRS their should be a unique requirement for every component if their are duplicate requirement for each component it is called as conflict requirement.
Example-In the documentation in page -10 customer has specified the amount test field should be consists of only integer where as in that same document customer has again specified that the amount field should consist of alphanumeric this type of mistake are called as conflict requirement.
Wrong Rquirments-The requirement are incorrect is called wrong requirement.
Example-In the requirement specification customer specified for the mobile text field it should contain integer and decimal.This type of requirement are called as wrong requirement.
Missing Requirment-A customer has hot specified requirement for the component then it is missing requirement.
Example-For the component user name the customer could have not specified requirement.
Once a review of CRS is done it will be given for the next stage is SRS meanwhile the acceptance testing team starts write acceptance test plan and test case.
Once the SRS is done it will will be given to the system testing team where they review SRS against CRS.
Later system testing team start writing system test plan and system test case, This continue till coding.
Verification-It is a process of checking are we building the product right.
Static Testing-Testing without execution of the source code is called as static testing.Activities which are involved in this testing are-Review requirement(SRS & CRS)
-Review Design(HLD & LLD)
-Review of source code.
Once a developer writes the source code they do the unit testing.
Unit Testing-Testing each and every lines of the source code is working or not.
Once a unit testing is done functional testing and system testing will be done.
Once system testing is done the application will be tested by the end users before the product is release to the market.
Validation-Process of checking are we building the right product.
Dynamic Testing-Testing with the execution of the source code is called as dynamic testing.Here we do the actual testing of application by giving the valid inputs.
Advantages of V Model- Requirement at the very inital stage.
-By modifying the requirement at very inital stage we can avoid the downward flow of defect.
-Each and every stages of test testing starts at very initial stage.
-By testing wach and every stages the customer can expect a very high quality of product.
-The work is done simultaneously in each and every stages.
Drawbacks
Documentation work is more.
Investment should be high.
Q-Why do we will go for V Model?
A-Customer is expecting very high quality of the software we go for the V model.
Q-For what short of application we go for the V model?
A-For long term project.
-For complex application.
it is all above the prevention of the defect.
Static Testing-This testing can be performed before the execution.
-Static testing is done before the code is deployed.
Dynamic Testing-This testing can be performed after after the execution.
-This testing is done after the code is deployed.
When the customer is new to the domain or he has a requirement but he does not have a clear picture of requirement in such case we go for prototype model.
Assuming the customer is new to domain or he has a requirement but not clear about the requirement.
The requirement will given Business Analyst(BA) in Coustomer Requiremet Specification(CRS) where later converted to Software Requirement Specification(SRS).
Once the SRS is completed design and develop prototype is done that is web designers they starts writing the dummy implementation using some of the scripting languages like HTML,CSS& AJAX.
Once a design of prototype is done the prototype testing will be done to ensure that the components are existing or not.
Once a prototype testing is done a dummy implementation will be sent to the customer for the review if the customer approves it will be driven by next activities.
NOTE In case if the customer modifies then the requirement need to be updated design and also prototype testing that is a lot of rework and time-consuming.
Once a designing is done developer starts writing source code by using programming language that is java,.NET etc..
Once a coding is done testing will be done on the application by giving valid or invalid inputs.
Once the application is tested the application will be installed in the customer place or on the customer server by build engineer or release engineer or installation engineer or developer.
Advantages of Prototype Model
Frequent communication between customer ,developer and the tester.
Beginning we set the expectation for the client.
Customer gets a opportunities in the beginning it self to ask for the requirement changes that is very easy to do before coding or testing.
Customer can get fair accurate product even he new to the domain.
We set the expectation of the client
Drawbacks of Prototype Model
There is a delay in starting the real-time project.
Investment should be high for the project.
In case if requirement changes then lots of rework need to be done time-consuming.
Testing is carried out after the coding.
Q-When do we go for prototype model?
A-Customer is new to the domain,
-Customer have requirement but he does not have clear picture of requirement.
-Testing is carried out after the coding.
Whenever their is a dependency in application or fetcher or module we follow spiral mode
Example-To develop an application in 3D we first need to develop in 2d.
The requirement are gathered for A where as later the crs will converted to SRS by the business analyst once the SRS complied the design(HLD & LLD) will be done.
Once the design is done the coding is done by the programmer or the developer using the programming language.
Once the coding is done the testing will be done.And once the complete A module is developed and tested the end user will starts testing the application before installing in customer place.And in case they identify the defect the defect will communicated to the developer where they fixed the defect.
Once the customer are time then only the requirement will be given for the next module that is B and this continues till n number of module with same activities.
Fetcher-It follows a spiral
Advantages-The requirement changes are allowed after develop one fetcher or one module then we can go and develop the next module of the project.At each Stage or release customer can sea the software.
Drawbacks-It is traditional model,
Developers are involved in testing,
Requirements are not verified,
Testing is the phase which will carried out after coding,If any major changes are done then lots of rework will happen that is time consuming.
Q-When do we go for spiral model?
A-When their is a dependency in application or fetcher or or module we go for spiral model
When the customer give requirements in stages we go for spiral model.
Q-If you have 2 module A and B, If you have identified a major defect in module B what will be your testing approach?
A-If a major defect is identified in module B then the defect will send to the developers for fixing.Once the defect is fixed i am going to retest the defect first and later i am going to test module A.Because in fixing the major defect it should not impact the related fetcher of the application.
Q-If you have two module A and B and their is a minor change in module A what will be the test approach?
A-First i am going to test the newly added requirement in module A where as i am not going to test the module B because as it is a minor it will not impact on the other related fetchers.