User Tools

Site Tools


dev:testing_code

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
dev:testing_code [2014/12/16 12:47] – created klussierdev:testing_code [2022/02/10 13:34] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ======Testing Code====== ======Testing Code======
-The Evergreen community can always use help from people interested in testing newly-contributed code. +The Evergreen community can always use help from volunteers willing to test newly-contributed code.  
 These [[https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=pullrequest+&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on|Evergreen bug fixes and code for new features]] are ready for testing. According to community guidelines, each piece of new code needs to be tested and get a sign-off from somebody else before it can be merged into Evergreen These [[https://bugs.launchpad.net/evergreen/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=pullrequest+&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on|Evergreen bug fixes and code for new features]] are ready for testing. According to community guidelines, each piece of new code needs to be tested and get a sign-off from somebody else before it can be merged into Evergreen
  
 Testing involves the following steps: Testing involves the following steps:
  
-   - Loading the code on a non-production server. If you cannot load code or cannot work with a local tech person to load code, you can submit a [[https://docs.google.com/forms/d/1ai8yL-XbCo3v8dxgMTCYcam_OtM93yzXv1WYF3MUm8Y/viewform?usp=send_form|Sandbox request form.]] +   - Loading the code on a non-production server. If you cannot load code or cannot work with a local tech person to load code, you can submit a [[https://docs.google.com/forms/d/1ai8yL-XbCo3v8dxgMTCYcam_OtM93yzXv1WYF3MUm8Y/viewform?usp=send_form|request for an Evergreen Sandbox.]] 
    - To avoid duplication of effort, add yourself to the "Assigned To" field in the Launchpad bug.    - To avoid duplication of effort, add yourself to the "Assigned To" field in the Launchpad bug.
    - If your testing finds the bug fix works as expected and does not break other functionality:    - If your testing finds the bug fix works as expected and does not break other functionality:
-     - [[dev:git#signing_off_on_one_or_more_commits|sign off on the code]] or add a comment to the Launchpad bug that says "I have tested this code and consent to signing off on it with my name, [enter name or consistent alias] and my email address, [enter email address]."+     - [[dev:git#signing_off_on_one_or_more_commits|sign off on the code through git]] or add a comment to the Launchpad bug that says "I have tested this code and consent to signing off on it with my name, [enter name or consistent alias]and my email address, [enter email address]."
      - Add a //signedoff// tag to the LP bug.      - Add a //signedoff// tag to the LP bug.
      - Remove yourself from the "Assigned To" field.      - Remove yourself from the "Assigned To" field.
    - If you discover problems when testing, add a comment to the Launchpad bug and remove yourself from the "Assigned To" field.    - If you discover problems when testing, add a comment to the Launchpad bug and remove yourself from the "Assigned To" field.
  
dev/testing_code.1418752075.txt.gz · Last modified: 2022/02/10 13:34 (external edit)

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.