السلام عليكم
لو تكرتمم ياريت انا بدور ع كتاب اسمه
Introduction to Software Testing
ل المؤلفين
~ Paul Ammann (Author), Jeff Offutt (Author)
فاذا حدا عنده نسخة او اي معلومة من وين ممكن اجيبه
يبقى مشكور جدااا
السلام عليكم
لو تكرتمم ياريت انا بدور ع كتاب اسمه
Introduction to Software Testing
ل المؤلفين
~ Paul Ammann (Author), Jeff Offutt (Author)
فاذا حدا عنده نسخة او اي معلومة من وين ممكن اجيبه
يبقى مشكور جدااا
مشكور جدا جدا جدا جدا
انا بحثــت كتير ما لقيتو غير شراء بفيزا
شكرا كتير
''اللهم إني أسالك إيمانا دائما وأسألك قلبا خاشعا وأسألك علما نافعا وأسألك يقينا صادقا وأسألك دينا قيما وأسألك العافية من كل بلية''
'اللهم أغفر للمؤمنين و المؤمنات و المسلمين و المسلمات الأحياء منهم و الأموات'
www.it-scoop.com
اختي eman 525 انا لم اجد لكي هذا الكتاب ..
ولكني لدي خلفية ولو قليلة على software testing اتمنى ان تفيدك
رغم بساطتها
ولكني سأحاول ان اجد لكي منهج للsoftwaren testing اوسع من ذلك.... والذي لدي من معرفة حول اختبار السوفت وير هو::::::
((Introduction
Software Testing can be defined: a process, or a series processes, designed to make sure
computer code does what is was designed to do and that it does not do anything unintended.
Software Testing Activities . . .
Analyzing and measuring the system s performance
Identifying possible errors (the goal is to find as many errors as possible)
Analyzing the risk of each error
Reporting the errors and ensuring they get fixed
The Goal of the Software Tester . . .
Finding errors
Finding errors and finding them as early as possible
Find errors, finding them as early as possible, and making sure they get fixed
The Testing Cycle is . . .
Developer sends
release to Tester
Tester finds defects, sends
bug report to developers
Developer fixes defects
and creates new release
So the testing cycle is not a
one time occurrence
The Software Tester Role . . .
Developing the Test Plan
Defining and managing required Test Resources
Creating and executing Test Cases
Analyzing Test Results
Creating Bug Report
Maintaining Test Statistics
Qualities of a good software Tester . . .
Testing Fundamentals
Black-Box and White-Box Testing . . .
These are two terms that software testers use to describe how they approach their testing.
QQUUAALLIITTIIEESS
Diplomatic
Great
Writing skills
Strong desire
for quality
organized
Can adopt Detail oriented
client s point of
view
Black-Box Testing (functional or behavioural testing)
The tester only knows what the software is supposed to do. The software tester
doesn't know the details of how the software works
He can't look in the box to see how it operates
If he types in a certain input, he gets a certain output. He doesn't know how or why
it happens, just that it does
White, Glass, or Clear-Box Testing (Structural Testing)
The software tester has access to the program's code and can examine it for clues to
help him with his testing
He can look inside the box to see how it operates
Based on what he sees, the tester may determine that certain numbers are more or
less likely to fail and can tailor his testing based on that information
Customer's point of view
Developer's point of view
Static and Dynamic Testing . . .
Black-box and white-box testing can be described as follows
Static testing: It refers to examining and reviewing something that's not running such
as documentation.
Dynamic testing: It refers to examining and reviewing something that's running such
as software.
Static and dynamic testing can be effectively achieved by applying two techniques as
follows:
Test-to-pass: you assure yourself that the software does what it's specified to do in
ordinary circumstances
Test-to-fail: you really assure only that the software shouldn t work when it shouldn t.
it's time to put on your sneaky, devious hat and attempt to find bugs by trying things
that should force them out
Creating the Test Cases . . .
A test case is A group of instructions for each test to be run on the system .
Testing is a two step progress:
FIND THE BUG
FIND THE CAUSE
Test case sections . . .
Purpose
Pre-requisites
Action to perform
Expected results
Actual results (pass / fail)
Notes
Post-requisites
What makes a good test case?
Complete and correct
Easy to read
Not redundant
The Bug Report . . .
Creating the Bug Report:
1)- Diplomacy and Details
- The tester needs to convince the developer to fix your bug:
Provide as many details as possible
Be as diplomatic as possible
the best tester is not the one who FINDS the most bugs or who
embarrasses the most programmers. The best tester is the one who get
the most bugs FIXED Kaner, 1988, p.15)
How would you write a test
case for this calculator?
Takes in 2 single or double digit
numbers and add them together
Number 1
Number 2
+
ANSWER
Calculator for adding 2 numbers
Instructor: Khalid Slhoub SE201 - Winter 2009
Page 52 of 53
2)- Short, descriptive summary
3)- Exact description of the error
How it deviated from the expected result
Include all error messages, etc.
Screen shots are very effective
4)- Set of numbered steps including what you did and what you saw
5)- Exactly what you typed, what files you used, what buttons you selected, etc
6)- Risk Analysis
Risk to the customer
How often will the customer see it
How many customers will see it
Does it block any functionality
Checking the Bug Report
Is there unnecessary information, personal opinions or anecdotes?
Is the report insulting? Are any words in the report potentially insulting?
Does the report seem too long? Too short?
Does it seem to have a lot of unnecessary steps?))
امنى ان يفيدك ذلك.. وبالتوفيق والنجاح
اختك فنو
:)