Where did these Defect Subroutines come from? Are they the same? Defects_Bug_MoveTo / Bug_MoveTo?
« Back
Tags:
Question ID: 104191
▲
3
▼
♥ 0

Where did these Defect Subroutines come from? Are they the same? Defects_Bug_MoveTo / Bug_MoveTo

Site Admin had an intern make some modifications and changes to QC and has come across a few issues:

Found there are a number of undocumented functions and sub-routines that are valid system-triggered events. These are triggered by QC when a user selects (or "moves to") a row in the Defects module (this was proven by inserting a MsgBox in both sub-routines, each with a separate message). However, only the Bug_MoveTo sub-routine is documented in the QC documentation – Defects_Bug_MoveTo is NOT. This is causing come concern. Note: In a project that was created from an empty database and not a copy of an existing project, this duplication does not occur.

Primary questions:

  • All of the "Defects_Bug_….." sub-routines and functions are still called as a part of valid system-triggered events, despite the fact that they are not documented; why did the duplication occur in the first place? And are they deprecated or is this for backward compatibility with Test Director 8.0?

  • Would you recommend removing them from the system? If yes, how to best execute and what are the ramifications of doing so (we want to manage the risk)? Note: We do not have a Dev/Test environment and need to use extreme caution. Backups are taken regularly.

Wanted to try to determine if this is a necessary result of the TD 8.0 to QC 10.0 upgrade.

Marked as spam
Posted by (Questions: 70, Answers: 111)
Asked on August 12, 2010 8:51 pm
43 views
Answers (1)
▲
3
▼
✔
Private answer

QUESTION:
Wanted to try to determine if this is a necessary result of the TD 8.0 to QC 10.0 upgrade.

ANSWER:
Yes, there was a naming convention change introduced in QC v9.2.
See documentation QCv9.2 Whats New excerpt Below.

QUESTION:
All of the ''Defects_Bug_.....'' sub-routines and functions are still called as a part of valid system-triggered events, despite the fact that they are not documented; why did the duplication occur in the first place?

ANSWER:
Upgraded project will see the additional subroutines.

QUESTION:
Are they deprecated or is this for backward compatibility with Test Director 8.0?

ANSWER:
This is for backwards compatibility.

QUESTION:
Would you recommend removing them from the system?

ANSWER:
In anticipation of deprecation, the code should be consolidated.

QUESTION:
How to best execute and what are the ramifications of doing so (we want to manage the risk)?

ANSWER:
Best Practice dictates NO direct changes to be made to any production environment. It is imperative to perform and validate ALL modifications in a Test Environment. Use the results and knowledge garnered from the Test Environment experience to create a customized Production Deployment Plan for your own environment.

Organizations that do not have Dev/Test environments can copy the projects and test modifications in the copy.
NOTE* All users will be logged out during the copy process.
NOTE* Large projects can take long periods of time to replicate. For these large projects, you can limit the amount of data you can choose to not include the various QC entity items on the selection step of the copy.

Marked as spam
Posted by (Questions: 0, Answers: 613)
Answered on August 12, 2010 9:08 pm
▲
0
▼
Sammy, thanks for the imput.
( at August 12, 2010 9:19 pm)
▲
0
▼
My Pleasure, as always
( at August 12, 2010 9:21 pm)
« Back
EyeOnTesting

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Got it!
X
Scroll to Top