Ruchityagi's Blog


CLIENT / SERVER TESTING
This type of testing usually done for 2 tier applications (usually developed for LAN)
Here we will be having front-end and backend.

The application launched on front-end will be having forms and reports which will be monitoring and manipulating data

E.g: applications developed in VB VC++ Core Java C C++ D2K PowerBuilder etc.
The backend for these applications would be MS Access SQL Server Oracle Sybase Mysql Quadbase

The tests performed on these types of applications would be
– User interface testing
– Manual support testing
– Functionality testing
– Compatibility testing & configuration testing
– Intersystem testing

WEB TESTING
This is done for 3 tier applications (developed for Internet / intranet / xtranet)
Here we will be having Browser web server and DB server.

The applications accessible in browser would be developed in HTML DHTML XML JavaScript etc. (We can monitor through these applications)

Applications for the web server would be developed in Java ASP JSP VBScript JavaScript Perl Cold Fusion PHP etc. (All the manipulations are done on the web server with the help of these programs developed)

The DBserver would be having oracle sql server sybase mysql etc. (All data is stored in the database available on the DB server)

The tests performed on these types of applications would be
– User interface testing
– Functionality testing
– Security testing
– Browser compatibility testing
– Load / stress testing
– Interoperability testing/intersystem testing
– Storage and data volume testing


SQL commands are divided into categories like DML (Data Manipulation language), DDL (Data definition language), TCL (Truncation control language) and DCL (Data control language). Here is a list of SQL commands:

1.       DML COMMANDS

  • INSERT
  • UPDATE
  • SELECT
  •  DELETE

2.       DDL COMMANDS

  • CREATE
  • ALTER
  • DROP

3.       TCL COMMANDS

  • COMMIT
  •  ROLLBACK

4.       DCL COMMANDS

  • GRANT
  • REVOKE

SMOKE TESTING

  • Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested.
  • A smoke test is scripted, either using a written set of tests or an automated test
  • A Smoke test is designed to touch every part of the application in a cursory way. It’s shallow and wide.
  • 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).
  • Smoke testing is normal health check up to a build of an application before taking it to testing in depth.

SANITY TESTING

  • A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.
  • A sanity test is usually unscripted.
  • A Sanity test is used to determine a small section of the application is still working after a minor change.
  • Sanity testing is a cursory testing, it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing.
  • Sanity testing is to verify whether requirements are met or not, checking all features breadth-first.

  • None
  • Infant Stroller: I lately found your blog/website and have truly loved reading through this and some of your other posts. I believed I'd dive out in the shadows and le

Categories

Archives

Follow

Get every new post delivered to your Inbox.