Archive for the ‘Testing’ Category

Comments Off

Draft test plan, close to IEEE 829


2009
04.12

All test plans are futile by nature, or else they dont represent the work of an tester trying to stretch the boundaries – find the weaknesses in the software..

Below are a draft test plan, with some of the most important issues desribed in IEEE 829.
(more…)

Comments Off

internetserviceteam.com


2009
04.11

locker room

internetserviceteam.com are one of the worlds worst sources to spam, according to digitalpoint.com. To lock for spammers are a bit like locking for breakout-specialists, its’s mind against mind.

Another thing about them: They were trying to use this site as host. (more…)

Comments Off

7 most important principles of software testing


2009
04.08

Farcus

  1. Test early. The later you wait, the more expensive it gets. The initial testing start at the initial meeting of the companys founders, keep on having small tests as early as possible.
  2. Testing show precense of defects, not absence.
  3. Exhausive testing is not possible within reasonable economical terms.
  4. Defects lump together. Find a defect: Look around it as well.
  5. Pesticide paradox: Bugs become imune against repeated tests.
  6. Testing is context dependant.
  7. Absence-of-errors-fallacy. No errors found during testing, proves only that none of the errors were found during testing.
Comments Off

Who is Pandega?


2009
04.03

Somebody are trying to cross-link this blog to a security issue in PHP3. The code below will give username and password to the person using the script – if the system is outdated securitywise. (more…)

Comments Off

IE8 – testresults


2009
03.21

Tested IE8 today and yesterday. The results are just as thrust-worthy as good old Windows ME: There are a few lacking features that make the thing a piece of garbage.

Personally, I loved ME. It was the epitome of Microsoft – filled tot he rim with nice features, and working stably when you found how to turn all the new features off.

IE8 was just as great. The installer took a long time to run each time, due to its demand to scan the computer for malicious software. The only thing failing with the installer, was the “install IE8″-step.

ie7-troubleshootingThe only change on the computer was a small web link on the desktop, to a page about troubleshooting failed installations of IE7. The web link was on a mixed-language site, but I suppose you’ll be able to read it – the relevant section is in English..

:-|

Comments Off

Exercise from the book “Software testing foundations”


2009
01.25

wet feetHere are Ketils personal notes from a walkthrough of the book “software testing foundations”, combined with notes on agile testing and parts from the wikipedia. Look if you wish, it’s as imperfect and unusable as such notes always should be.

2.1 Define the terms failure, fault and error

Failure := Desribes the event when a user experiencne a problem, a non-fulfillment of a given requirenment. Examples of failures are products that .

Fault := the cause of a failure

Error := A failure to complete a task, usually involving a premature termination (http://en.wiktionary.org/wiki/error)

2.2 What is defect masking

(more…)

Comments Off

Basic strategies for integration testing


2009
01.24

Here are a small listing of the basic integration strategies a test manager can use when he’s designing a test strategy:

Top-down integration:

The test starts with the top level component of the system that calls the components but is not called itself (the top component).

Stubs must substitute all non-finished lower-level components, integration proseede with the lower-leel components as soon as they are produced.

Advantage: Test drivers are not needed, the highere-level components are the test-drivers.

Disadvantage: This is a very costly method, because of the amount of stubs to be produced.

(more…)

Comments Off

Test tools


2009
01.23

Tools are available for every phase of the test process, helping the tester to automate test activities or improve the quality of the activities.

Use of a test tool is only benefical wen the test process is defined and controlled.

The introduction of a test tool must bee supported by information, training, coaching. You dont have any use of a plier if you dont know how it is used..

:-)

Comments Off

Test management, summary


2009
01.23

Development activities and testing activities should be organized independently. This separation should be as clear as possible.

Depending on the tasks to be executed, staff with social competence is required. Low social competence = somebody gets humiliated. Humiliation will block effective testing and production.

The test managers tasks are: The initial planning of the tests, plus further planning, monitoring and controlling the different test cycles.

The test plan is where the test manager describes and explains the test strategy. The international standard IEEE 829 provides a checklist for format and content

There are a break-even-point between testing costs and the estimated costs of a faulty product. The costs for both issues have to be balanced through priorities.

One of the best metods to prioritize the effort, is by risk assessment. Risk-based testing uses information about identified risk fro planning, specification, preparation and execution of tests. All major elements of the test trategy are determined on the basis of risk, just the same way as risk-based development.

Measurable exit criteria define when testing can be stopped. Without given exit criteria, testing might stop randomly.

The basis for an effecient test process, are formed by incident management and configuration management.

The incident-reports must be collected, systematized and kept throughout the entire project. The relevant parts must be updated to follow the development – just as any agile documents must be updated and changed throughout any development process.

Standards contain specifications and recommendations from peers. Following such standards utilizes the experience of the peers, even if it is neither mandatory or eligible to follow them strictly.

Testing is creativity..

Comments Off

Incident report template


2009
01.23

Attribute

Meaning

Identification

ID / number Identifier for each report
Test object Name of the test object
Version Version of the test object
Platform HW/SW platform tested
Reporter Who dunnit
Responsible reporter Who’s to blame
Date When it was done

Classification

Status State and history for processing the report
Severity The severity of the problem (classification)
Priority Is it 1., 2. or 3. priority to correct what’s found here?
Requirement What customer requirement is not fulfilled due to this problem?
Problem source When was this problem initially reported? – during what project phase?

Problem description

Test Case I know I’m a nut case, this is the link to the test case of the problem (name, number)
Problem description The Problem
Comments List of comments from the involved staff
Defect correction The changes required to correct the defect
References Ref. Related report #

I know, this is a incomplete and unsatisfying template. But there are few complete and satisfying things when it comes to this issue.. Beer with me ;-)


Bad Behavior has blocked 56 access attempts in the last 7 days.