Ticket #40 (closed planned_task: obsolete)
PLATFORM_STANDARDS_MANUAL_TESTS_R1
| Reported by: | Astea | Owned by: | boyan |
|---|---|---|---|
| Priority: | 3 | Milestone: | M03_PRE3 |
| Component: | SOPHIE_PLATFORM | Version: | 2.0 |
| Keywords: | Cc: | ||
| Category: | PLATFORM | Effort: | 1 |
| Importance: | 20 | Ticket_group: | |
| Estimated Number of Hours: | Add Hours to Ticket: | ||
| Billable?: | Total Hours: | ||
| Analysis_owners: | deyan | Design_owners: | boyan |
| Imp._owners: | Test_owners: | ||
| Analysis_reviewers: | todor | Changelog: | |
| Design_reviewers: | deyan | Imp._reviewers: | |
| Test_reviewers: | Analysis_score: | 3.5 | |
| Design_score: | 1 | Imp._score: | 0 |
| Test_score: | 0 |
Description
wiki page: PLATFORM_STANDARDS_MANUAL_TESTS_R1 - effort: 1d
Change History
comment:1 Changed 16 years ago by deyan
- Status changed from new to s1a_analysis_started
- Analysis_score set to 0
- Test_score set to 0
- Design_score set to 0
- Owner changed from Astea to deyan
- Imp._score set to 0
comment:2 Changed 16 years ago by deyan
- Status changed from s1a_analysis_started to s1b_analysis_finished
30m
comment:4 Changed 16 years ago by todor
- Status changed from s1b_analysis_finished to s1c_analysis_ok
- Analysis_reviewers set to todor
- Analysis_score changed from 0 to 3.5
i'm not sure if the effort will be enough in order to be fulfilled the task requirements
comment:7 Changed 16 years ago by boyan
- Design_owners set to boyan
- Owner changed from deyan to boyan
- Status changed from s1c_analysis_ok to s2a_design_started
taken for design
comment:8 Changed 16 years ago by boyan
- Design_owners set to boyan
- Status changed from s2a_design_started to s2b_design_finished
done in 1h
comment:9 Changed 16 years ago by deyan
- Status changed from s2b_design_finished to s1c_analysis_ok
- Design_score changed from 0 to 1
The design and the implementation of this task doesn't meet the task requirements - requirements say different pages should be created. Also there are some other problems with the document. One of the biggest in my opinion is that you recreate (do an implementation) a document that is used without a design review!
- Test cases may contain prerequisites - of course opening Sophie and creating a new book won't be a step in every test case. They should be marked as Step0
- Talking about "obeying rules" in bug reports is a good wish, but does not make any sense since we are allowing people to commit bugs on their own. Unless you think someone will go after and moderate tickets, this is useful. Requirements to bug reporting should be minimalistic as reporting bugs will be done not only by people with technical knowlege. This also applies to bug categories where we definitely need an uncategorized.
- Using bold and italics is not used by many developers, probably using them here makes this page a little inconsistant with all of the wiki contents. We use headings and bullets.
- Sentences like "When writing manual tests, do not forget the general guideline of the project: Work towards the goal! " are not in place - this is a serious project, not a daycare.
- Sentences like "Non-integer scores are STRONGLY disencouraged." are not in place - this is a serious project, not a daycare. You do not have to SHOUT to get understood.
I'm putting one because of disrespecting the requirements. (In platform standards design there was no explanation what to do in this case.)
comment:10 Changed 16 years ago by deyan
- Design_reviewers set to deyan
forgot to add design reviewers
comment:11 Changed 15 years ago by deyan
- Status changed from s1c_analysis_ok to closed
- Resolution set to obsolete
Batch update from file query-obsoleted.csv
Note: See
TracTickets for help on using
tickets.
taken for analysis