Project

General

Profile

Task #6739

Story #6730: deploy v2 MNWebTester

design versioning options and user workflow

Added by Rob Nahf about 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
d1_integration
Target version:
Start date:
2015-01-06
Due date:
% Done:

100%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

both how to name the test cases (put version in the class name, or use package namespace for versioning?), and how to specify the parameter in the web GUI.

History

#1 Updated by Rob Nahf almost 7 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 80

capitalized version should be in the test name, instead of package name. This allows multiple versions for a test. For example: MNAuthenticationV1V2.java.

Implemented this and modified test selector to be more direct and allow multiple selection from the Web Tester.

Split out tests by API, instead of tier.
split out authentication tests (SSL tests)

will split out content checks (resourceMap parsing, etc.)

#2 Updated by Rob Nahf over 6 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 80 to 100
  • translation missing: en.field_remaining_hours set to 0.0

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)