SQL BASICS BY LOKRE

SQL BASIC QUERIES

SQL>Conn /as sysdba
(Conn Username/Password)


1. SQL>Show user;

USER is SYSTEM

2. SQL>select banner from v$version;

BANNER
----------------------------------------
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Product
PL/SQL Release 10.2.0.1.0 - Production
"CORE 10.2.0.1.0 Production"
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 – Production


3. SQL>Select global_name from global_name;

GLOBAL_NAME
XE

4. SQL> Select * from tab;

It displays all the tables from Database.


5. SQL> Select * from all_users;

It shows the list of users.

6. SQL>Clear scr;

It clears the screen.


There are two types of tables in Oracle

1. SYSTEM TABLES (or) DATA DICTIONARY TABLES (or) PREDEFINED TABLES.
2. USER DEFINED TABLES.


SQL – STRUCTURED QUERY LANGUAGE


DDL (Data Definition Language)

CREATE, ALTER, DROP, RENAME, TRUNCATE

DML (DATA MANIPULATION LANGUAGE)

INSERT, UPDATE, DELETE

DQL (DATA QUERY LANGUAGE)

SELECT

TCL (TRANSACTIONAL CONTROL LANGUAGE)

COMMIT, ROLLBACK


DCL (DATA CONTROL LANGUAGE)

GRANT, REVOKE


LINKS TO SQL :

http://st-curriculum.oracle.com/tutorial/SQLDeveloper/index.htm
http://www.vacic.org/lib/sql/
http://beginner-sql-tutorial.com/sql.htm
http://www.w3schools.com/sql/default.asp


PL/SQL
http://www.plsql-tutorial.com/

LOKREs NOTES

BASICS:


DBMS – DATA BASE MANAGEMENT SYSTEM.

RDBMS -- RELATIONAL DBMS


DATA --- Collection of Files.

Files  .txt (Notepad)
.doc(Ms-Word)
.ppt(Ms- PowerPoint)
.xls (Ms- Excel)
.pdf(Acrobat)

And some more example you can find in the below links for file extensions

http://www.fileinfo.com/filetypes/common

http://en.wikipedia.org/wiki/List_of_file_formats



DATA BASE:

Logical container to store the data in the form of tables, objects & Procedures, functions etc.









ODBC  Open Data base Connectivity.



2- Tier Architecture :



FRONT END ODBC BACK END
Java, .Net (Developers) DATABASE
(SQL, MYSQL, DB2, SYBASE, FOXPRO)

Database Developers





It is named as 2-Tier Architecture because it has Front end and Back end.


Example:

Front End -- >> Gmail’s Home page (User Interface page)
Back End -- > > Data stored here (Your emails and data files, attachments etc)


If you’re using java, then it’s JDBC connectivity.
ADO. NET connectivity is for DOT NET.






3 – Tier Architecture:



APPLICATION SOFTWARE
|
|

FRONT END ODBC BACK END
(Developers) DATABASE
(SQL, MYSQL, DB2, SYBASE, FOXPRO)

Database Developers


It is named as 3-Tier Architecture because it has
Application Software, Front end and Back end.


APPLICATION SOFTWARE:

Application software, also known as an application or an "app", is computer softwaredesigned to help the user to perform specific tasks. Examples include enterprise software, accounting software, office suites, graphics software and media players. Many application programs deal principally with documents. Apps may be bundled with the computer and its system software, or may be published separately. Some users are satisfied with the bundled apps and need never install one.




4 – Tier Architecture:



APPLICATION SOFTWARE
(Desktop Applications)
|
|

FRONT END ODBC BACK END
(Developers) DATABASE
(SQL, MYSQL, DB2, SYBASE, FOXPRO)
|
| Database Developers
Web Browser
(ASP. NET, PHP)


It is named as 4-Tier Architecture because it has
Application Software, Front end, Back end and Web Browser.










DATABASE MANAGEMENT SYSTEM (DBMS)

There are 3- types of DBMS:

HDBMS -- Hierarchal DBMS
NDBMS -- Network ’’
RDBMS -- Relational ’’

RDMS -- 12 Rules (E F CODD RULES).

http://en.wikipedia.org/wiki/Types_of_DBMS

RDBMS ----

ORACLE – PL/SQL -- 80% Market (Platform Independent) -12 EF Codd Rules
SQL SERVER -- 20% market
MS ACCESS
MY SQL
DB2
SYBASE
FOXPRO
PORT GRE SQL







Oracle PL/SQL follows 12 EF codd Rules.
http://en.wikipedia.org/wiki/Codd's_12_rules

DB2, FOXPRO, PORT GRE SQL follows only 4/5 E F CODD RULES.


Platform Independent: It works on any platform (UNIX, Linux, and Windows).



GUI – GRAPHICAL USER INTERFACE (Windows 7/XP)


NOT GUI – Command prompt.














ORACLE stands for

OAK RIDGE AUTOMATIC COMPUTER LOGICAL ENGINE.


ORACLE

1. USER.
2. DEVELOPER.
3. ADMIN/ADMINISTRATOR.

USER -- SQL knowledge is enough.
DEVELOPER -- SQL, PL/SQL knowledge is enough.
ADMIN - He should know the following point below:
1. Sql
2. Pl/Sql
3. How to take a backup.
4. Maintenance of data
5. Tuning
6. Restore
7. Replication
8. Data Guard

Replication is the process of sharing information so as to ensure consistency between redundant resources, such as software or hardware components, to improve reliability, fault-tolerance, or accessibility.


Data Guard:

Providing the security to database.








ORACLE FLAVOURS

1. ENTERPRISE EDITION – This is for Companies.
2. EXPRESS EDITION (XE) – This is for STANDALONE (for single users/Single system).
3. STANDARD EDITION – This is for globally.
4. WORK GROUP – This is for Office purpose.


VERSIONS OF ORACLE:

1979 – Version 1
1990 – 6.0 Version
1995 – 7.0
1996 – 7.1
1997 – 7.2
1998 – 8i (‘i’ stands for internet. It is a first internet version and platform independent).

2000 – 9i
2004 –10g (‘g’ stands for GRID COMPUTING).
2007 – 11g


Grid computing is a term referring to the combination of computer resources from multiple administrative domains to reach a common goal.

http://ss64.com/ora/syntax-versions.html

SOFTWARE TESTING

TESTING:

Identifying defects in the product.

Variance in between expected and actual product.

Eg: Expected is--- > Customer/Client will expect from company.
Actual is --- > What the company designs/develops/manufactures.



SOFTWARE:

Software is an application (Apps) or Set of programmes. It might be a

1> Web application. (Websites)
2> Desktop application. (Eg. Microsoft’s Operating System and it’s applications(Ms- Office))
3> Mobile application.



SOFTWARE TESTING:

The process that involves the operations of system.

(Or)

The Process of executing a program with the intent of finding errors.

There are 2 ways of Testing:

1. MANUAL TESTING
2. AUTOMATION TESTING.


WHY DON’T DEVELOPERS INVOLOVE IN TESTING?

A developer thinks in a positive way of developing. So, He don’t take a chance of thinking in negative way i.e., Defects.






WHY SOFTWARE TESTING?

To find out the bugs in the newly developed software.
To deliver defect free product to reach the customer/client/user expectations & needs.
To satisfy the customer needs.



TESTERS ROLE:

TESTER –> (Test the) -- APPLICATION – (Find the) DEFECTS – (Sends to) DEVELOPER



IMPORTANT NOTE:

ERROR --- > OCCURS IN A PROGRAM. (While developing or writing).
DEFECT --- > After implementation, Tester finds and sends to developer.
BUG --- > Defect accepted by Developer.

HISTORY OF S/W TESTING

Usage of the term "bug" to describe a defect has been a part of engineering jargon for many decades, perhaps even from the times of Tomas Edison. In software testing it always refers to September 9th, 1945, when the first real bug traced an error in the Harvard Mark II, an electromechanical computer. This bug was carefully removed and taped to the log book (see picture: The First "Computer Bug" ). This history is usually connected with the name Grace Murray Hopper, who described this event in the computer log.

Let us start the history of testing from the 50s, when the first modern programming language was designed: FORTRAN, the "FORmula TRANslator", invented by John W. Backus, and the first FORTRAN compiler was delivered in April 1957.

The history of computers starts form Analytical Engine created in 1842 by Charles Babbage enlisted the help of Lady Ada Lovelace as a translator. Ada, called herself 'an Analyst'
Charles Babbage, (1791 – 1871) was an English mathematician, philosopher, inventor and mechanical engineer who originated the concept of a programmable computer [Wiki]

1950 - 1960 1960 - 1970 1970 - 1980 1980 - 1990 1990 - 2000 2000 - 2010


1950-1960

1953 Dr Edward Deming published: Management’s responsibility for the Use of Statistical Techniques in Industry. He outlined 14 quality principles in this book.
1954 - The first truly mass-produced computer IBM 650 was marketed.
1955 - Grace Hopper created Flow-matic, the first high-level language.
1955 the first computer user group, called SHARE was formed.
Until 1957 it was the debugging oriented period, when there was no clear difference between testing and debugging.
[History Software Testing Back to Top]


1960-1970

1960 - Digital Equipment Corporation (DEC) marketed the PDP-1,considered the first commercial minicomputer
1960 - Block structure for better organization of code in the programs was introduced in Algol.
January 1, 1961 Computer Programming Fundamentals,Mcgraw-hill Inc; 1 edition by Herbert Leeds and Jerry Weinberg, describes software testing
1962 The first computer science departments established at Purdue and Stanford.
1962 Douglas Engelbart invented the computer mouse. (The keyboard was first invented and patented in 1868 by Christopher Latham Sholes.)
1963 Adam, Carl – wrote his dissertation with topic: Petri Nets.
1964 The American National Standards Institute (ANSI) officially adopted the ASCII (American Standard Code for Information Interchange) character code.
1966 Book:"Computer Programming Fundamentals" by Herbert D. Leeds and Gerald M. Weinberg
1967 Herm Schiller creates the first software code coverage monitor, called Memmap, at IBM Poughkeepsie. It supports 360/370 Assembler language. [Richard Bender]
1968 The first introduction of the term software engineering and structured programming.
1969 Edgar F. Codd introduced the concept of the relational system.
1969 The first automatic teller machine (ATM) was put in service.
1969 Richard Bender and Earl Pottorff created the first static and dynamic analysis tools using data flow analysis for improved test coverage. It increases code based coverage by 25% over the statement and branch coverage criteria in Memmap. (search for article called "How Do You Know When You Are Done Testing" that addresses this.) Note: this work was given the first Outstanding Invention Award ever handed out by IBM for breakthroughs in software engineering.
[History Software Testing Back to Top]


1970-1980
1971 -The IEEE Computer Society was founded.
1971 Milt Bryce first applied the term "methodology" to systems development.
1972 Alan Kay developed Smalltalk the first object-oriented programming language.
1972 Dennis Ritchie and Brian Kernighan developed C language.
1973 The first computer user groups was founded in Boston.(disbanded in 1996)
1973 ( or 1970?) Elmendorf, William R. introduced cause – effect graphs in functional testing.Elmendorf is also the person who first created equivalence class testing with boundary analysis.
1973 Gruenberger, F., introduced the triangle testing problem in his article: Program testing, the historical perspective.
1974, 5 April first software related standard: "MIL-S-52779 Software Quality Program Requirements" was issued.
1974 The first international computer chess tournament is won by the Russian KAISSA program.
1975 November Hamlet, R.G., Compiler-based Systematic Testing.
1976 Software reliability : principles and practices by Glenford J. Myers
"The goal of the testers is to make the program fail. If his test case makes the program or system fail, then he is successful; if his test case does not make the program fail, then he is unsuccessful."
"A good test case is a test case that has a high probability of detecting an undiscovered error, not a test case that show that the program works correctly." - Glenford Myers.

1976 Fagan, Michael E, published his article " Design and Code Inspections to reduce errors in program development." IBM System Journal Vol. 15, No.3, 1976 pp.182-211. (developed Code Inspection process)
1976 December - The cyclomatic complexity metric for measure complexity of a routine, originally described by Tom McCabe.
1977 Atari 2600 a video game console was released.
1977 Requirements Based Testing was introduced.
1978 CompuServe pioneered the wide use of e-mail.
1978 Hayes developed the Smartmodem for the first personal computers, it took the market in 1981.
1979 Philip Crosby,published his book "Quality is free" in McGraw-Hill Publishing.
1979. - The separation of debugging from testing was initially introduced by Glenford J. Myers In his book "The Art of Software Testing" he provided definition of software testing widely used now and the first clear explanation of equivalence classes, boundaries and other testing principles .
[History Software Testing Back to Top]


1980-1990
1980 Epson MX-80 became the best-selling dot-matrix printer.
1982 William Edwards Deming offers a theory of management based on his famous 14 (quality principles) Points for Management.
1983 Boris Beizer, "Software Testing Techniques" 1st edition.
1983 Lotus 1-2-3 spreadsheet for DOS was released.
1984 Tetris game was created.
1985, July Commodore finally released the Amiga 1000 personal computer at a retail price of $1295
1985 Excel spreadsheet application launched in by the Microsoft Corporation.Excel in the best friend of a tester.
1986 Apple Macintosh Plus with 1MB of RAM was introduced.
1986 - The particulars of the Six Sigma methodology were first formulated by Bill Smith at Motorola
1987 ISO 9000 quality standards were released.
1987 The Zachman Framework for descriptive represntations of an enterprise IT environment.
1988 Eudora was the first non-mainframe e-mail client.
1988 B. W. Boehm introduced a spiral model for software development.
1988 ISO/IEC 12207- "Software Life Cycle Processes" was proposed and published in August 1995.
1988 Dave Gelperin and William C. Hetzel classified the phases and goals in software testing.
1989 WordPerfect Corporation released the WordPerfect 5.1 for DOS.
[History Software Testing Back to Top]


1990-2000
In the early 1990s, continuous quality improvement (CQI) methods were implemented.
From early 1990's Bug Tracking and Version Control tools become popular.
1991, June - publication of ISO 9000-3: "Quality management and quality assurance standards"
Part 3: Guidelines for the application of ISO 9001 to the development, supply and maintenance of software.
1991- Linus Torvalds wrote his own unix kernel for the popular now Linux operating system.
1992, October, IBM introduced the first ThinkPad model 700.
1993 Software Quality Automation, Inc., Woburn, Mass., has unveiled SQA TeamTest, a GUI testing tool implemented on a team/workgroup model.
Rational purchased SQA TeamTest v6.1
IBM acquired Rational corporation on December 2002.
1993 HP LaserJet 4L was introduced.
1993 Mosley, Daniel J., introduced Decision table method
1994, October 13, Marc Andreessen launched Web browser called Mosaic Netscape 0.9.
1994, 5 December DoD issued MIL-STD-498, software Development and Documentation.
1995, July - Microsoft released the Windows 95 operating system.
1997 UML (Unified Modeling Language) was introduced by James Rumbaugh,Grady Booch and Ivar Jacobson.
1998 Rational unified process (RUP) was introduced.
1998 K. Zambelich published article “Totally Data-Driven Automated Testing“
1999, May How (and how not) to implement Data Driven Automation using Rational Robot , by Carl Nagle SAS Institute, Inc
see details on http://safsdev.sourceforge.net/DataDrivenCompilation.html
1999 -Poston, Robert developed a specification-based test generation tool
[History Software Testing Back to Top]


2000-2010
2000, March First Keyword Driven Automation was implemented using Rational Robot
See details on http://safsdev.sourceforge.net/DataDrivenTestAutomationFrameworks.htm#KeywordDrivenAutomationFrameworkModel
Rational Unified Process (RUP) Methodology (Develop iteratively, with risk as the primary iteration driver)

END Software testing history.

Check out this link :

http://www.testingthefuture.net/2010/10/the-history-of-software-testing/

SOFTWARE TESTING PROJECT SCHEME

TESTING LIFE CYCLE

SOFTWARE TESTERS CAREER