Why We Need Testers?

There are number of reasons for which we need dedicated testers and not developers:

1. The perception between a developer and a tester is different. Tester has an attitude to break and will cover both positive flows and negative flows.

2. Tester not only have a very good understanding of various flows and modules in an application, he also applies his skill and expertise to find bugs.

3. A tester not only concentrates on functionality but also on other issues like usability, GUI, Database

We always need a Separate Testing team to Ensure the Quality of the Product. Reason Being:

A Developer will never tend to find a Bug in his code, where as Tester’s main motive is to find as many bug as possible.
A developer can overlook minor issues where as a Tester will not overlook even the minor things, ensuring that cutomer is fully satisfied.

1.we need testers because developers are not good testers.
2.Misunderstanding will not be detected ,because the checker will assume that what the other individual heard from him was incorrect.
3.Improper use of the development process may not be detected because the individual may not understand the process.
4.The individual may be blinded into accepting erroneous system specifications and coding because he falls into the same trap during testing that led to the introduction of the defect in the first place.
5. Information services people are optimistic in their ability to do defect free work and thus sometimes underestimate the need for extensive ttesting.
6.Without formal division between development and test, an individual may be tempted to improve the system structure and documentation, rather than allocate that time and effort to the test.

UNIX Command Summary

There are MANY commands available for you in a UNIX shell account. A list of them follows (in no particular order). Remember, you can always read the manpage on each command for more information.

ls …………….. show directory, in alphabetical order
logout …………. logs off system
mkdir ………….. make a directory
rmdir ………….. remove directory (rm -r to delete folders with files)
rm …………….. remove files
cd …………….. change current directory
man (command) …… shows help on a specific command
talk (user) …….. pages user for chat – (user) is a email address
write (user) ……. write a user on the local system (control-c to end)

pico (filename) …. easy to use text editor to edit files
pine …………… easy to use mailer
more (file) …….. views a file, pausing every screenful

sz …………….. send a file (to you) using zmodem
rz …………….. recieve a file (to the unix system) using zmodem

telnet (host) …… connect to another Internet site
ftp (host) ……… connects to a FTP site
archie (filename) .. search the Archie database for a file on a FTP site
irc ……………. connect to Internet Relay Chat
lynx …………… a textual World Wide Web browser
gopher …………. a Gopher database browser
tin, trn ……….. read Usenet newsgroups

passwd …………. change your password
chfn …………… change your “Real Name” as seen on finger
chsh …………… change the shell you log into

grep …………… search for a string in a file
tail …………… show the last few lines of a file
who ……………. shows who is logged into the local system
w ……………… shows who is logged on and what they’re doing
finger (emailaddr).. shows more information about a user
df …………….. shows disk space available on the system
du …………….. shows how much disk space is being used up by folders
chmod ………….. changes permissions on a file
bc …………….. a simple calculator

make …………… compiles source code
gcc (file.c) ……. compiles C source into a file named ‘a.out’

gzip …………… best compression for UNIX files
zip ……………. zip for IBM files
tar ……………. combines multiple files into one or vice-versa
lharc, lzh, lha …. un-arc’ers, may not be on your system

dos2unix (file) (new) – strips CR’s out of dos text files
unix2dos (file) (new) – adds CR’s to unix text files

UNIX Command Dictionaries

The UNIX manual is mostly on line and the UNIX `man’ command is used to display parts of the manual. Typing

man [command] (CR)
will yield information in an almost readable format during a IBM Telnet session. The problem is that you have both UNIX and CMS paging the output. You respond to the UNIX paging prompt `:’ with a `(CR)’ return for a new page, `d (CR)’ for a short new page, u (CR)’ for a short page up (back), or `q (CR)’ to quit. For the CMS paging prompt `holding’, respond with the designated `Clear-key’. If you are using IBM Telnet, then `man [command]‘ usually produces poor output for the head of the display. The version `man -blou [command] (CR)’ should remove underscoring and other backspacing for printing at UIC, but does not work completely. For a quick overview of a command try the `-q’ quick option:

man -q command] (CR)
Alternatively,

man [command] > [file] (CR)
is useful for redirecting the output to a file that can later be transfer back to CMS for printing (e.g. by `printdoc’). The UNIX no paging `-r’ option does not work in a CMS session, so the CMS user has to press both the `Return-key’ for a new UNIX `man’ page or the `Clear-key’ for a new CMS page depending on the odd UNIX prompt or the CMS “HOLDING” prompt, respectively.

This abridged UNIX dictionary is only intended to be a short enough list to get you started without being bewildered by the enormous UNIX manuals, but with enough commands to be able to do something useful. For more information use the `man’ command or refer to some of the UNIX texts. UNIX is a trademark of Bell Laboratories.

The format is

[command] [generic operand] : [Definition.]

along with a carriage return `(CR)’ for each command. DO NOT FORGET that almost all UNIX commands must be in lower case. Do not attempt to learn all of this at once, but read some of it and try it out at an actual computer session.

Introduction of System Testing

System testing is testing conducted on a complete, integrated system to evaluate the system’s compliance with its specified requirements. System testing falls within the scope of Black box testing, and as such, should require no knowledge of the inner design of the code or logic.

As a rule, System testing takes, as its input, all of the “integrated” software components that have successfully passed Integration testing and also the software system itself integrated with any applicable hardware system(s). The purpose of Integration testing is to detect any inconsistencies between the software units that are integrated together (called assemblages) or between any of the assemblages and the hardware. System testing is a more limiting type of testing; it seeks to detect defects both within the “inter-assemblages” and also within the system as a whole.

Types of system tests

The following examples are different types of testing that should be considered during System testing:

• Functional testing
• User interface testing
• Usability testing
• Compatibility testing
• Model based testing
• Error exit testing
• User help testing
• Security testing
• Capacity testing
• Performance testing
• Sanity testing
• Regression testing
• Reliability testing
• Recovery testing
• Installation testing
• Maintenance testing
• Accessibility testing

What is Test Scripts

A test script is a short program written in a programming language used to test part of the functionality of a software system. Any test that is written as a short program is regarded as an automated test. Test scripts written as a short program can either be written using a special automated functional GUI test tool or in a well-known programming language (such as C++, Tcl, Expect, Java, Perl, Python, or more recently, Ruby).