3,054
edits
Changes
From SME Server
Jump to navigationJump to searchSME Server:Documentation:QA:Verification (view source)
Revision as of 22:59, 25 February 2021
, 22:59, 25 February 2021no edit summary
{{Languages}}
Not all bugs require code fixes but a substantial part of them do. An important part of the QA process is verifying that the issue addressed in a bug is fixed when any of the code is changed.
Not all bugs require code fixes but a substantial part of them do. An important part of the QA process is verifying that the issue addressed in a bug is fixed when any of the code is changed.
We try our best not to overlook things but it can happen, proper verification is important to reduce the risk of such things slipping through. Therefore we try and stick to a certain work flow when doing verification.
We try our best not to overlook things but it can happen, proper verification is important to reduce the risk of such things slipping through. Therefore we try and stick to a certain work flow when doing verification.
Since the development team and resources are rather limited it is difficult enough to try and fix all bugs raised, let alone also verify them. Since you do not need to be a developer to verify the fixes that have been produced this guide is written to help all members of our community to help us in the process of verification, it is a vital part of the ongoing maintenance of SME Server.
Since the development team and resources are rather limited it is difficult enough to try and fix all bugs raised, let alone also verify them. Since you do not need to be a developer to verify the fixes that have been produced this guide is written to help all members of our community to help us in the process of verification, it is a vital part of the ongoing maintenance of SME Server.
{{Warning box|KOOZALI SME 10 beta1. To install a test machine, see [[Testing_Environments]].}}
1. Install and configure a server with iso.
2. smeserver-yum, e-smith-base and smeserver-support in smeupdates-testing needs to be updated first with their dependancies :
yum update smeserver-yum smeserver-support e-smith-base --enablerepo=smeupdates-testing
3. after reboot apply full :
yum update
An update to tinydns & dnscache did break dns.
You have to manually start them after a reboot and then update.
Verification should be done with yum update —enablerepo=smeupdates-testing packagename.
Before that you must use the same commande but with smeserver-yum e-smith-base smeserver-support to ensure you have the last running scripts.
===General work flow===
===General work flow===
#. short summary of what the new package has achieve, eg. fixed this or that.
#. short summary of what the new package has achieve, eg. fixed this or that.
===Upgrade the new rpm===
===How upgrade the new packages===
{{Note box|Of course we are doing good code but we can brake your system, so you are strongly advised for doing verification on a virtual SME Server.}}
{{Note box|Of course we are doing good code but we can brake your system, so you are strongly advised for doing verification on a virtual SME Server.}}
The bug report will detail the exact package and version needed. These are normally in smeupdates-testing and can be installed by
The bug report will detail the exact package and version needed. These are normally in smeupdates-testing and can be installed by :
yum --enablerepo=smeupdates-testing update <package>
for example
for example
The above process is documented in the comment field of a bug using the following template, more information on the steps and the template sections can be found below.
The above process is documented in the comment field of a bug using the following template, more information on the steps and the template sections can be found below.
'''VERIFICATION TEMPLATE'''
= ENVIRONMENT:
= ENVIRONMENT:
= PROBLEM FIXED?:
= PROBLEM FIXED?:
[Repeat steps carried out under TESTING above.
[Repeat steps carried out under TESTING above]
= VERIFIED OR REOPEN:
= VERIFIED OR REOPEN:
====Suggested release notes====
====Suggested release notes====
If you feel capable please suggest the information we can put in the release notes in one or two lines, if you cannot please leave this empty, or for instance specify it is to be determined by specifying ''T. B. D.''.
If you feel capable please suggest the information we can put in the release notes in one or two lines, if you cannot please leave this empty, or for instance specify it is to be determined by specifying ''T. B. D.''.
===Abbreviated Verification===
Only to be used when circumstances dictate urgency in completing multiple verification in a short time.
= CURRENT VERSION INSTALLED:
[rpm -qa <package name>]
If its an actual Bug show the issue if you can, showing steps taken, otherwise just show it is working, location, any templates,
config settings, db settings etc that will or may be changed
= UPDATED VERSION INSTALLED:
Update to new package, show steps taken
# yum updat/install e-smith-base --enablerepo=smeupdates=testing or smetest (check for latest
version, it evolves rapidly just now with changes)
# reboot reconfig if required, good idea just in case
and:
[rpm -qa <package name>]
Show its working if possible and/or no errors evident in loges etc
= VERIFIED OR REOPEN:
[Problem fixed, then VERIFIED - not fixed, then REOPEN]
Note: if you do not have rights to toggle resolution, someone will do it for you
= DOCUMENTATION IMPACT:
[Does something need documentation, eg a db or new procedure? if affirmative, please provide details, someone will later punt to
docteam for action]
[[Category:SME Server]][[Category:Howto]][[Category:Help]][[Category:Developer]]
[[Category:SME Server]][[Category:Howto]][[Category:Help]][[Category:Developer]]
