Ken TestMan is ...

  • a central database - Store your test documentation in one place;
  • a web based interface - Allow your users to work together wherever they are.

Ken TestMan does ...

Ken TestMan allows you to document and manage your testing artefacts throughout the full testing lifecycle, from creating testable Requirements, through developing Test Cases, to executing tests and recording Defects.

  • Requirments - define the system being tested
  • Test Cases - describe the tests to run
  • Test Suite - a logical grouping of Test Cases
  • Execution - record the results of running the Test Cases
  • Defects - document the failures and track their resolution

Benefits

More Work in Less Time: Your team can quickly and easily share their work and re-use the work of others. Copy Test Cases from other projects, include other people's Test Cases in your Test Suite.

Better Documentation of your Testing: Create Test Cases directly from Requirements; create them quickly using the short form; even create them during the test execution. All of these make it easy to document the tests you will be/are running.

Visibility of Testing: Which requirements aren't covered, how many tests have been written, how many have passed/failed etc.

Meet Deadlines: You can instantly see the problem areas for testing; Test Cases aren't being written quickly enough; the defect discovery rate is too high etc . Which means you can plan to address them; more resources, reduce scope, extend deadline etc.

Informed Decisions: Real time reports and statistics ensure that you have the information you need to make decisions. Never go to a meeting uninformed again!

Features

Projects Ken supports many concurrent projects with users able to be assigned a different role on each project.

Component Tree A Windows like folder tree to allow you to organise your test cases in a way that makes sense to you.

Test Cases Document the procedure, expected results, priority etc. Add you own custom fields to ensure you capture information imortant to you.

Test Suites Group logically releated Test Cases into a Test Suite, this could be by functional area ot by what's released in a build etc.

Executions Execute a Test Suite and record the results of each Test Case.

Reports View reports to see your progress, how many test cases created, how many executed, how many failed etc.

Testing isn't an isolated activity, so Ken TestMan does more

Requirements Document the requirements of the system under test, see the coverage of requirements by test cases.

Builds The details of each build can be captured in Ken Testman; you can even attach a release note to the build.

Environments Record details of your test environments, including build they're running, see the history of changes.

Defects The inbuilt defect management tool links to environments, builds and execution results, so the developer can see exactly what you were doing, where and with which version of the code.