Page 119 - DCAP405_SOFTWARE_ENGINEERING
P. 119
Software Engineering
Notes
Language Example program
"C" #include <stdio.h>
void main() {
printf("Hello World");
}
C++ #include <iostream>
int main()
{
cout << "Hello World";
return 0;
}
Pascal program helloworld (output);
begin
writeln('Hello World');
end.
Oracle PL/SQL CREATE OR REPLACE PROCEDURE helloworld AS
BEGIN
DBMS_OUTPUT.PUT_LINE('Hello World');
END;
Java class helloworld
{
public static void main (String args [])
{
System.out.println ("Hello World");
}
}
Perl #!/usr/local/bin/perl -w
print "Hello World";
Basic print "Hello World"
7.5.3 Testing Principles
Whether you have performed testing for a number of years or have just started, this is a course
you really need to take. You will be exposed to a number of testing practices; some of which will
likely be new to you. Drawing on his over 30 years of experience with all aspects of the software
process, Dr. Hanna will use real life examples to illustrate every point. The course will introduce
you to a Scenario-Based test design methodology. The course also covers the different types of
testing performed at each phase of the software lifecycle and the issues involved in these types
of tests, clarifies testing terminology, and much more.
Principles of Good Testing
Complete testing isn’t possible: No matter how much you test, it is impossible to achieve
total confidence. The only exhaustive test is one that leaves the tester exhausted!
Test work is creative and difficult: You must understand and probe what the system is
supposed to do. You must understand and stress the limitations and constraints. You must
understand the domain and application in depth.
Testing is risk-based: We can’t identify all risks of failure. Risk assessments indicate how
much to test and what to focus on.
112 LOVELY PROFESSIONAL UNIVERSITY