Test Strategy

This is the basic test strategy applied to Quality Spy development (and maintainance).

Test Subject

Quality Spy (program, plugins, setup).

Why?

Check the stability and usability of new features (verification and pre-validation). Check for regression bugs.

When?

Feature tests occucur as fast as possible after development. Regression tests should be executed before a release. No scheduling.

Where?

No specific requirements.

How?

Manual testing; split up into secnario testing and functional testing. Unit tests and full UI integration tests also exist, but only as an additional security and faster feedback. Main testing will be manual. With time the automated part should increase.

With

Primary Tool: Quality Spy + Mantis Integration

Needed Equipment (clean VMs):

  • Windows 8
  • Windows 7
  • Windows XP

Different Windows themes (Classic, XP, Aero)

Freemind 0.8, 0.9 / latest version

TestLink installed on a web server to create test data.

Automation: NUnit and TestStack.White

Who?

Me – Andreas Kleffel.

I will try to get feedback from other persons as a validation. But the primary testing is not done by other persons than me.

Acceptance Criteria

New functions are stable (or labeled as “beta”), no fatal regressions are introduced. At least smoketests should be executed for each even minor release. Minor bugs are acceptable.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s