|Anonymous | Login | Signup for a new account||2019-12-13 02:59 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005273||TestLink||New Feature||public||2012-10-08 12:47||2012-10-08 16:53|
|Product Version||1.9.4 (2012 Q3 - bug fixing)|
|Fixed in Version|
|Summary||0005273: New test case type (Session based testing)|
|Description||Since no other big test case management tools can deal with reporting of session based test (exploratory testing see http://bit.ly/SHWeu5 [^]) this could be a opportunity for TestLink to be that tool.|
In Testlink this could be done as "Only" a new kind of test case.
Today we have Manual and Automatic. Please bare with me, I don't know that much about the integration of those terms behind the scenes, please in-light me in case i'm wrong.
As in scripted testing, a tester starts out with a "Charter" A "Charter" that briefly describes some logistics about the session he/she is about to test. A charter could be seen a bit as a test case, but with some more details in it.
When working with session based testing a tester compiles a session report. A session report is consisting of the following:
+-#TEST DESIGN AND EXECUTION
+-#BUG INVESTIGATION AND REPORTING
+-#CHARTER VS. OPPORTUNITY
+-Upload or link to
In the test report describing the progress you will then from the above, be able to make a "summery graph" with something like:
#Number of sessions completed
#Number of problems found
#Function areas covered
#Percentage of session time spent setting up for testing
#Percentage of session time spent testing
#Percentage of session time spent investigating problems
Ill be happy to help developing this with a little help from you in case this is an somehow easy task. I guess this might involve some DB and frontend programming, therefore please help me discuss this new feature.
|Steps To Reproduce||See description|
|Additional Information||New feature|
|Tags||No tags attached.|
|QA Team - Task Workflow Status||TBD|
edited on: 2012-10-08 16:51
With description provided is not clear what are the impacts.
If only a new test type is needed then this is absolutely trivial.
But IMHO this is not the request, then:
1. subject has to be rewritten, becuase you do not need JUST a new test type, but a whole new concept.
2. please provide an openoffice or word document with detailed requirements, including screen mockups, reports and so on
3. do not use meaningless versions when reporting, you can use ONLY OFFICIAL RELEASED versions
|2012-10-08 12:47||dylf||New Issue|
|2012-10-08 16:50||fman||Note Added: 0017624|
|2012-10-08 16:51||fman||Note Edited: 0017624||View Revisions|
|2012-10-08 16:53||fman||Priority||urgent => normal|
|2012-10-08 16:53||fman||Product Version||2.0 Alpha 1 => 1.9.4 (2012 Q3 - bug fixing)|
|Copyright © 2000 - 2019 MantisBT Team|