QA testing with ms project macros..

[Joy]

we have a toolabar with macros in VBA for MS project
now, we are doing QA testing on it. is there any advice on how to do QA
testing?? any suggestion is welcome...thanks

 

[John]

we have a toolabar with macros in VBA for MS project
now, we are doing QA testing on it. is there any advice on how to do QA
testing?? any suggestion is welcome...thanks

Joy,
It all depends on what you mean by "QA testing". If I take you
literally, QA stands for quality assurance and QA testing is not the
same as function testing. In that context checking the "quality" of your
toolbar and the macros behind it means that you need to verify that
everything works per the requirements laid out for it. Also, if there
are any company directives or protocols that must be followed for this
type of thing, does your implementation meet those.

If you simply want to run tests on your implementation to verify stable
functionality, I would run the following tests as a minimum.
A. If users have different Windows operating systems (e.g. XP, Vista,
etc.), make sure it works with all configurations.
B. The same is true for different versions of Project.
C. Are there various type of Project files, (i.e. single, master,
linked, etc.)? Make sure it works with all file types. There may be
special considerations if you are using Project Server. In that case,
you may want to post to our sister newsgroup at,
microsoft.publi.project. server
D. How is configuration controlled, including who is authorized to
update the macros, toolbar icons, etc.?

There may be other test requirements that may be appropriate based on
your unique environment but the above will get you started in the right
direction.

Hope this helps.

John
Project MVP

 

[Mike Glen]

Hi Joy,

If I might add to John's advise, any macros need documentation. The test
should be: if the person(s) who created the macros left your company, could
anyone pick it up and understand why it was constructed in that way, based
on what policies, and the macros should include any explanations of how the
macros work. The macros should be scattered with explanatory notes to show
these factors, including details of the variables and their coded names and
what the procedures do or set out to do. I hope you can see the importance
of such documentation for solving future problems or development.

Mike Glen
MS Project MVP
See http://tinyurl.com/2xbhc for my free Project Tutorials

 

[Joy]

thank you very much

Joy,
It all depends on what you mean by "QA testing". If I take you
literally, QA stands for quality assurance and QA testing is not the
same as function testing. In that context checking the "quality" of your
toolbar and the macros behind it means that you need to verify that
everything works per the requirements laid out for it. Also, if there
are any company directives or protocols that must be followed for this
type of thing, does your implementation meet those.

If you simply want to run tests on your implementation to verify stable
functionality, I would run the following tests as a minimum.
A. If users have different Windows operating systems (e.g. XP, Vista,
etc.), make sure it works with all configurations.
B. The same is true for different versions of Project.
C. Are there various type of Project files, (i.e. single, master,
linked, etc.)? Make sure it works with all file types. There may be
special considerations if you are using Project Server. In that case,
you may want to post to our sister newsgroup at,
microsoft.publi.project. server
D. How is configuration controlled, including who is authorized to
update the macros, toolbar icons, etc.?

There may be other test requirements that may be appropriate based on
your unique environment but the above will get you started in the right
direction.

Hope this helps.

John
Project MVP

 

[Joy]

thank you very much

Hi Joy,

If I might add to John's advise, any macros need documentation. The test
should be: if the person(s) who created the macros left your company, could
anyone pick it up and understand why it was constructed in that way, based
on what policies, and the macros should include any explanations of how the
macros work. The macros should be scattered with explanatory notes to show
these factors, including details of the variables and their coded names and
what the procedures do or set out to do. I hope you can see the importance
of such documentation for solving future problems or development.

Mike Glen
MS Project MVP
See http://tinyurl.com/2xbhc for my free Project Tutorials

 

[Mike Glen]

You're welcome, Joy

Mike Glen
MS Project MVP
See http://tinyurl.com/2xbhc for my free Project Tutorials