Beruflich Dokumente
Kultur Dokumente
doc
1. Software Quality
Important points:
- The requirements of the software are infect the foundation from which quality is
measured ;
-The standard development criteria or requrements that guide the manner in which the
software is engineered or developed ;
- whether the software meets these standards or not
Now the factors means the real issues behind the scene
-correctness - does it do what I want?
- reliability - does it do it accurately?
- efficiency - will it run efficiently on my hardware?
- integrity - is it secure?
- usability - is it designed for the user?
MORE>>>>>>
1. Software Quality factors
Product revision:
- maintainability - can I fix it? Means kamran that with the help of qa does it helps in
easy maintaining of the product or not.
- flexibility - can I change it? Means kamran that if I need to change the product or alter,
add or update ( like Microsoft windows 98 to win 2000 or win xp) can it be done or at
what leve it can be done)
Product transition:
The word transition means * let say if you are leaving from home to University. Now the
time between “when u leave home and before srriving Uni.* “ is the transition period”.
In other words, when the product start changing to the time just before it reaches it final
stage.
- portability - will I be able to use it on another machine? Easy to understand, like usb
pen drive.
- reusability - will I be able to reuse some of the software?
- interoperability - will I be able to interface it with another system? Like Bluetooth
mobile devices can it work in all mobile or nokia only.
http://www.testingcenter.com/c100mr00.html
To detect when this happens, we keep a set of tests (the Regression Test Set, or the RTS
for short) containing tests of important things that used to work okay. We run the RTS
after each set of changes to make sure that these things still work.
That's it.
The problem is to do regression testing correctly, so that it solves more problems than it
creates.
(2) It can also detect undesirable side effects caused by changing the operating
environment. For example, hardware changes, or upgrades to system software such as
the operating system or the database management system
1-The first question is almost always easy. We simply test whatever the change is
supposed to do,
2- "Did It Break Anything Else ". (a) what's broken, and (b) how would we know that?
Answer: run the Regression Test Set (RTS).
3-"Is the RTS still okay?", is often overlooked, but it's one of the things that can get you
in trouble.
Summary:
• Regression testing means rerunning tests of things that used to work to make sure
that a change didn't break something else
• The set of tests used is called the Regression Test Set, or RTS for short
• It's enormously helpful when you change an application, change the environment,
and during integration of pieces.
• Regression testing is a simple concept, but it needs to be done just right to work in
the real world.
Testing is based on behaviour of the application . what it does/ produces etc. Also in
black box testing testers does not require code language
More example read this: if u feel easy or leave it as this much is enough to get the basic
of this. http://www.webappsec.org/lists/websecurity/archive/2008-05/msg00025.html
*Black Box testing is also very strong at identifying errors of omission and
unintended/surprising emergent behaviours
4. White Box testing is the act of verifying the internal workings of a piece of software
with reference to structure and/or down to the algorithmic(functioning) level. There are
many different types of testing that fall under "White Box" testing. (e.g "structural
verification")
White Box testing is primarily focused on verifying that the design structure follows an
expected or ideal structure, and that the implemented algorithms perform the units of
work that they are planned too. White Box testing is very strong at identifying errors of
commission.
OTHER TESTINGS
1. "Vuln test" aka vulnerability (WEAKNESS) testing == subset of Black Box testing.
Most commonly means to locate the artifacts of
exploitable conditions & behaviors in software. False positive prone without human
analysis, due to the fact the artifacts are often behavioral inference, and may not in fact
indicate a security defect at all.
http://www.aptest.com/glossary.html
Ad Hoc Testing: A testing phase where the tester tries to 'break' the system by
randomly trying the system's functionality. Can include negative testing as well.
Automated Testing: