Ticket #1482 (closed planned_task: obsolete)

Opened 17 years ago

Last modified 15 years ago

SCS_TEST_TRACKING_MAINTENANCE_R8

Reported by: Milen Owned by: todor
Priority: 3 Milestone: M09_BETA1
Component: PROJECT_COMMUNITY Version: 2.0
Keywords: Cc:
Category: SCS Effort: 0.5
Importance: 90 Ticket_group:
Estimated Number of Hours: 0 Add Hours to Ticket: 0
Billable?: yes Total Hours: 0
Analysis_owners: milen Design_owners: milen, vanya
Imp._owners: milen, vanya Test_owners:
Analysis_reviewers: todor Changelog:
Design_reviewers: todor Imp._reviewers: todor, todor
Test_reviewers: Analysis_score: 4
Design_score: 3 Imp._score: 3.5
Test_score: 0

Description

wiki page: SCS_TEST_TRACKING_MAINTENANCE_R8 - effort: 0.5d

Change History

comment:1 Changed 16 years ago by milen

  • Status changed from new to s1a_analysis_started
  • Total Hours set to 0
  • Analysis_score set to 0
  • Test_score set to 0
  • Reporter changed from Astea to Milen
  • Add Hours to Ticket set to 0
  • Design_score set to 0
  • Billable? set
  • Owner changed from Astea to milen
  • Estimated Number of Hours set to 0
  • Imp._score set to 0

comment:2 Changed 16 years ago by milen

  • Status changed from s1a_analysis_started to s1b_analysis_finished

comment:3 Changed 16 years ago by todor

  • Status changed from s1b_analysis_finished to s1c_analysis_ok
  • Analysis_reviewers set to todor
  • Analysis_owners set to milen
  • Analysis_score changed from 0 to 4

good analysis don't forget to list the added testcases in the implementation section and fill your name in the analysis owners.

comment:4 Changed 16 years ago by milen

  • Status changed from s1c_analysis_ok to s2a_design_started

comment:5 Changed 16 years ago by vanya

  • Design_owners set to milen, vanya

comment:6 Changed 16 years ago by milen

  • Status changed from s2a_design_started to s2b_design_finished

comment:7 Changed 16 years ago by todor

  • Status changed from s2b_design_finished to s2c_design_ok
  • Design_score changed from 0 to 3
  • Design_reviewers set to todor

Following things must be keep in mind when implementing the task:

  • The numbering of the test case steps is messed in some test cases. In the implementation it should be corrected when there is more than one option this is noted as (1.1. followed by 1.2. if necessary 1.3.1. and 1.3.2. etc.)
  • When the test case ends with save and load book, it is good to begin with create or load existing book (that depends on the specific test case). Because if the tester do the changes on the book desktop he/she can not save the book.
  • In the test case for rotation it is good to mention the rotation degrees (30 degrees for single click).
  • In the test case for the chaining must be added text that is long enough to fill the created text frames, otherwise we can not know whether chaining works or not.
  • The test case for unchaining must be corrected step 2 can be divided and it must be explained with more details the results of unchaining (what happens with the text, how it behaves).
  • There are some test cases ending with "Save and reload the book." this should be separated.
  • The deleting of chained text frames must behave differently, when deleting Frame C, Frame A is chained with Frame B. Explain how the text behaves (it rearranges in the following frames). Deleting one frame of the chain must not unchain all frames.
  • Testing of the Links must include opening the book in preview mode, and checking if the trigger and action are executed correctly.
  • In Book Resources Manipulation->Inserting Resources "main line" must be replaced with "Insert from the file menu". And steps 2-4 must be "Create new book or open existing"., like it is in the other test cases, same applies to the last test case.

comment:8 Changed 16 years ago by milen

  • Status changed from s2c_design_ok to s3a_implementation_started
  • Imp._owners set to milen, vanya

comment:9 Changed 16 years ago by vanya

  • Status changed from s3a_implementation_started to s3b_implementation_finished

comment:10 Changed 16 years ago by todor

  • Status changed from s3b_implementation_finished to s2c_design_ok
  • Imp._score changed from 0 to 2
  • Imp._reviewers set to todor

for some of the test cases the recommendations left in the design part are not followed, and their design was pasted directly without fixing.

comment:11 Changed 16 years ago by todor

  • Owner changed from milen to todor
  • Status changed from s2c_design_ok to s3a_implementation_started
  • Imp._score changed from 2 to 3.5
  • Imp._reviewers changed from todor to todor, todor

comment:12 Changed 16 years ago by todor

  • Status changed from s3a_implementation_started to s3b_implementation_finished

comment:13 Changed 16 years ago by todor

  • Status changed from s3b_implementation_finished to s3c_implementation_ok

the implementation fixes the design according to the comments, but this task took more than a week. don't forget to change the ticket status when working on something.

comment:14 Changed 15 years ago by deyan

  • Status changed from s3c_implementation_ok to closed
  • Resolution set to obsolete

Batch update from file query-obsoleted.csv

Note: See TracTickets for help on using tickets.