From Fedora Project Wiki

< FWN‎ | Beats

(create fwn 235 qa beat)
(create fwn 288 draft)
 
(48 intermediate revisions by the same user not shown)
Line 3: Line 3:


In this section, we cover the activities of the QA team<ref>http://fedoraproject.org/wiki/QA</ref>. For more information on the work of the QA team and how you can get involved, see the Joining page<ref>http://fedoraproject.org/wiki/QA/Join</ref>.
In this section, we cover the activities of the QA team<ref>http://fedoraproject.org/wiki/QA</ref>. For more information on the work of the QA team and how you can get involved, see the Joining page<ref>http://fedoraproject.org/wiki/QA/Join</ref>.
We apologize for the lack of a QA section for the last few issues of FWN: the QA team was very busy with Fedora 16 validation testing. This issue catches up with the QA team news from the last several weeks.


Contributing Writer: [[User:Adamwill|Adam Williamson]]
Contributing Writer: [[User:Adamwill|Adam Williamson]]
Line 8: Line 10:
<references/>
<references/>


=== Instructions and process for moving bug reports upstream ===
=== Test Days ===
 
In the past few weeks, we finished up the Fedora 16 Test Day schedule, with Graphics Test Week taking place at the start of September<ref>http://fedoraproject.org/wiki/Test_Day:2011-09-06_Nouveau</ref> ref>http://fedoraproject.org/wiki/Test_Day:2011-09-07_Radeon</ref> ref>http://fedoraproject.org/wiki/Test_Day:2011-09-07_Radeon</ref>, virtualization test day taking place on 2011-09-15<ref>http://fedoraproject.org/wiki/Test_Day:2011-09-15_Virtualization</ref>, another i18n desktop test day on 2011-09-22<ref>http://fedoraproject.org/wiki/Test_Day:2011-09-22_I18n_Desktop</ref>, an ABRT test day on 2011-09-26<ref>http://fedoraproject.org/wiki/Test_Day:2011-09-26_ABRT</ref>, a power management test day on 2011-09-29<ref>http://fedoraproject.org/wiki/Test_Day:2011-09-29_PowerManagement</ref>, printing test day on 2011-10-06<ref>http://fedoraproject.org/wiki/Test_Day:2011-10-06_Printing</ref>, Fedora packager plugin for Eclipse test day on 2011-10-13<ref>http://fedoraproject.org/wiki/Test_Day:2011-10-13_Fedora_Packager_for_Eclipse</ref>, and Cloud SIG test day on 2011-10-20<ref>http://fedoraproject.org/wiki/Test_Day:2011-10-20_Cloud_SIG_Test_Day</ref>. Most of these test days passed off successfully with the work of the developers behind them, despite the QA team being very busy, so many thanks to those who organized and carried out these events, and those who turned up to do the testing.


[[User:Ankursinha|Ankur Sinha]] began a discussion<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/092018.html</ref>, <ref>http://lists.fedoraproject.org/pipermail/test/2010-July/092036.html</ref> on providing instructions for users on the Wiki for reporting bugs to upstream bug trackers. [[User:Johannbg|Jóhann Guðmundsson]] felt that this was the wrong approach<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/092040.html</ref> and that it should be the responsibility of package maintainers to submit reports upstream when appropriate. In general, though, the group felt that providing instructions for users would be helpful in at least some cases, and Ankur said he would work on a draft of such a page<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/092091.html</ref>.
The Fedora 17 Test Day cycle has not yet started. We welcome proposals for test days for the Fedora 17 cycle, and we usually accept all the proposals that are made. You can propose a test day for almost anything, and organize it yourself following the handy guide we provide<ref>http://fedoraproject.org/wiki/QA/SOP_Test_Day_management</ref>, or alternatively we can help out with the organization of the event. Information on how to propose a test day is available on the Wiki<ref>http://fedoraproject.org/wiki/QA/Test_Days/Create</ref>.


<references/>
<references/>


=== Rawhide acceptance testing ===
=== Fedora 16 preparation ===


[[User:Jlaska|James Laska]] reported<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/092095.html</ref> on the first automated Rawhide acceptance test plan<ref>http://fedoraproject.org/wiki/QA:Rawhide_Acceptance_Test_Plan</ref> run for Fedora 14, and linked to the full results<ref>http://fedoraproject.org/wiki/Test_Results:Fedora_14_Pre-Alpha_Rawhide_Acceptance_Test_1</ref>. The run exposed four bugs, which were significant enough that the test images could not be declared 'last known good'.
As mentioned above, Fedora 16 release validation took up almost all of the QA team's time during the last few months, with very challenging Beta and Final releases. There were a total of 12 candidate builds for Beta and Final combined, and the whole team put in tireless work running the set of validation tests against each build and then investigating and verifying the large number of blocker bugs identified. The team was able to contribute to the release eventually going ahead with only a one week slip to the Beta schedule and no slip of the Final schedule, a considerable achievement in the light of the many complex changes in the Fedora 16 feature list.


<references/>
<references/>


=== Proven testers ===
=== Release criteria updates ===
 
Largely as a result of the Fedora 16 validation process, there were several adjustments and additions to the release criteria in recent weeks. After discussion of the proposed kickstart / unattended installation release criterion concluded, [[User:Adamwill|Adam Williamson]] reported that he had committed his proposed modifications<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102599.html</ref>. He also committed a change to reflect the increased priority of EFI installations from Fedora 17 onwards<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102600.html</ref>.


[[User:Adamwill|Adam Williamson]] announced<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/092075.html</ref> that he had updated the Wiki proven testers material, making the main page<ref>http://fedoraproject.org/wiki/Proven_tester</ref> cover all aspects of the project (based on his previous draft mentioned in last week's issue) and turning the JoinProvenTesters page into a redirect to it. Later in the week he updated the instructions again<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/092101.html</ref>.
Adam also passed on a suggestion from [[User:Pjones|Peter Jones]] to improve the clarity of the virtualization criteria<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102601.html</ref>. After an extensive discussion, an elegant wording suggestion from Albert Graham<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102636.html</ref> was eventually accepted and committed<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103680.html</ref>.
 
[[User:Tflink|Tim Flink]] raised the question to what extent support for Xen virtualization should be included in the release criteria<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/103127.html</ref>. After a similarly enthusiastic discussion, it was eventually agreed that Xen DomU support - effectively, the ability to install successfully as a Xen guest - should be a Final release criterion<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103678.html</ref>.
 
Adam also proposed downgrading some rarely-used kickstart deployment methods from Beta to Final in the criteria, requiring only the most commonly-used to be working at Beta stage<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103557.html</ref>.
 
Finally, Adam proposed a criterion for i18n (translation) issues<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103588.html</ref>. After discussion, the proposal was agreed upon at a blocker review meeting later in the week<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103679.html</ref>.


<references/>
<references/>


=== AutoQA package acceptance testing ===
=== Update policy changes ===


During the QA weekly meeting of 2010-07-12<ref>http://fedoraproject.org/wiki/QA/Meetings/20100712</ref>, [[User:Wwoods|Will Woods]] explained that the AutoQA team had decided to consider automating the package update acceptance test plan<ref>http://fedoraproject.org/wiki/QA:Package_Update_Acceptance_Test_Plan</ref> as its highest priority. They felt this would provide a very visible and useful example of the potential of AutoQA as soon as possible. Automated package acceptance testing would prevent packages with certain types of serious problems, such as broken dependencies, from being accepted as updates. Will had identified clear areas of focus which are necessary to implement automated package acceptance testing, and these can be tracked on the AutoQA roadmap<ref>http://fedorahosted.org/autoqa/roadmap</ref>.
In September, [[User:Karsten|Karsten Hopp]] raised the issue of a security update for Fedora 14 which had been languishing in the updates-testing repository for some time<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102493.html</ref>. [[User:Adamwill|Adam Williamson]] explained that the amount of testers working on older releases was limited, and that the actual karma requirements for updates to be accepted were controlled by FESCo (the Fedora engineering steering committee), not the QA group<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102497.html</ref>. [[User:Cra|Chuck Anderson]] noted that he had the update in question installed, but was struggling for lack of information on how to test it properly<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102503.html</ref>. [[User:Sundaram|Rahul Sundaram]] suggested that Karsten file a ticket with FESCo to raise the issue<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102502.html</ref>, and Karsten did<ref>http://fedorahosted.org/fesco/ticket/664</ref>.
 
That ticket was merged with another similar one reported by Doug Ledford<ref>http://fedorahosted.org/fesco/ticket/667</ref>, which became a topic of concern to FESCo. After several rounds of discussions, FESCo first decided to relax the requirements for critical path updates somewhat by allowing them to be sent through to the stable repository without the 'required' karma after a period of two weeks had elapsed<ref>http://fedorahosted.org/bodhi/ticket/642</ref>, and later proposed removing the requirement for critical path updates to receive positive karma from a proven tester<ref>http://fedorahosted.org/fesco/ticket/667#comment:26</ref>, effectively a proposal to end the proven tester system, as this is the only function it serves.
 
The QA group discussed this proposal at the weekly meeting of 2011-11-07<ref>http://fedoraproject.org/wiki/QA/Meetings/20111107</ref>, agreeing that, while they had some reservations about the proposal, they were not definitely opposed to it, and recognized that critical path updates not receiving the currently-required karma is a significant problem.
 
<references/>
 
=== Update candidate notification ===
 
Samuel Greenfeld asked if there was any system to notify testers of new candidate updates for specific packages, and to determine what packages are being actively used on a system<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102981.html</ref>. There were no takers for the second question, but for the first, [[User:Adamwill|Adam Williamson]] suggested using yum parameters that would allow one to specify only certain packages be pulled from the updates-testing repository<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102982.html</ref>, and [[User:till|Till Maas]] pointed out that Bodhi can actually provide per-package RSS notifications<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102992.html</ref>.


<references/>
<references/>


=== Localization testing ===
=== Proven tester meetings ===
 
As a response to the concerns about candidate updates not receiving enough karma, [[User:Kevin|Kevin Fenzi]] ran a series of weekly proven tester meetups<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/102869.html</ref> from 2011-09-21 to 2011-10-26. Recaps of these meetings are available in the mailing list archives<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/103000.html</ref> <ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103341.html</ref> <ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103585.html</ref> <ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103840.html</ref> <ref>http://lists.fedoraproject.org/pipermail/test/2011-October/104043.html</ref>.


[[User:Igor|Igor Pires Soares]] announced<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/092029.html</ref> that he would be working to update the Fedora 13 localization results template<ref>http://fedoraproject.org/wiki/QA:Fedora_13_l10n_Results_Template</ref> for Fedora 14 use at FUDCon Santiago, and asked for feedback and ideas on improving it. [[User:Jlaska|James Laska]] suggested<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/092094.html</ref> a page to explain the general testing procedure, and asked where test results are recorded. Igor accepted the general procedure idea, and explained that the template was intended to allow local teams to record results in whatever way they felt most appropriate<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/092096.html</ref>.
Kevin also proposed an updates-testing-info mailing list, containing only the mails about new packages in updates-testing<ref>http://lists.fedoraproject.org/pipermail/test/2011-September/103163.html</ref>. However, the consensus was against the idea, as it was felt that it was easy enough to simply filter the desired mails from the test mailing list for those who did not want to read the other traffic.


<references/>
<references/>


=== Boot menu release criterion proposal ===
=== QA group representation at FUDCon Pune ===


After a contentious first Fedora 14 blocker bug review meeting<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/092147.html</ref>, [[User:Adamwill|Adam Williamson]] proposed two alternative ways to cover boot menu functionality in the release criteria<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/092148.html</ref>. He suggested either having a basic test of essential functionality (the installer eventually boots without manual interaction) at the Alpha stage and a more advanced test (the graphical boot menu appears as intended) at Beta or Final stage, or simply having the more advanced test at Alpha stage. [[User:Jlaska|James Laska]]<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/092152.html</ref> and [[User:Jkeating|Jesse Keating]]<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/092150.html</ref> both came down in favour of simply requiring the menu to work correctly at Alpha stage.
[[User:Ankursinha|Ankur Sinha]] asked whether anyone from the QA team would be present at the upcoming FUDCon in Pune, India and able to do a presentation on the group's activities<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103712.html</ref>. [[User:Adamwill|Adam Williamson]] replied that unfortunately none of the Red Hat team would be at the conference, but encouraged Ankur to take a shot at giving a presentation himself<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103728.html</ref>. A S Alam then stepped up to volunteer to lead a QA session<ref>http://lists.fedoraproject.org/pipermail/test/2011-October/103739.html</ref>. His session was scheduled for 2011-11-04<ref>http://fudcon.in/sessions/fedora-testing</ref>, but we have no report on the event - if you were present, please write to the mailing list and let us know how it went!


<references/>
<references/>

Latest revision as of 05:10, 17 November 2011

QualityAssurance

In this section, we cover the activities of the QA team[1]. For more information on the work of the QA team and how you can get involved, see the Joining page[2].

We apologize for the lack of a QA section for the last few issues of FWN: the QA team was very busy with Fedora 16 validation testing. This issue catches up with the QA team news from the last several weeks.

Contributing Writer: Adam Williamson

  1. ↑ http://fedoraproject.org/wiki/QA
  2. ↑ http://fedoraproject.org/wiki/QA/Join

Test Days

In the past few weeks, we finished up the Fedora 16 Test Day schedule, with Graphics Test Week taking place at the start of September[1] ref>http://fedoraproject.org/wiki/Test_Day:2011-09-07_Radeon</ref> ref>http://fedoraproject.org/wiki/Test_Day:2011-09-07_Radeon</ref>, virtualization test day taking place on 2011-09-15[2], another i18n desktop test day on 2011-09-22[3], an ABRT test day on 2011-09-26[4], a power management test day on 2011-09-29[5], printing test day on 2011-10-06[6], Fedora packager plugin for Eclipse test day on 2011-10-13[7], and Cloud SIG test day on 2011-10-20[8]. Most of these test days passed off successfully with the work of the developers behind them, despite the QA team being very busy, so many thanks to those who organized and carried out these events, and those who turned up to do the testing.

The Fedora 17 Test Day cycle has not yet started. We welcome proposals for test days for the Fedora 17 cycle, and we usually accept all the proposals that are made. You can propose a test day for almost anything, and organize it yourself following the handy guide we provide[9], or alternatively we can help out with the organization of the event. Information on how to propose a test day is available on the Wiki[10].

  1. ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-06_Nouveau
  2. ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-15_Virtualization
  3. ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-22_I18n_Desktop
  4. ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-26_ABRT
  5. ↑ http://fedoraproject.org/wiki/Test_Day:2011-09-29_PowerManagement
  6. ↑ http://fedoraproject.org/wiki/Test_Day:2011-10-06_Printing
  7. ↑ http://fedoraproject.org/wiki/Test_Day:2011-10-13_Fedora_Packager_for_Eclipse
  8. ↑ http://fedoraproject.org/wiki/Test_Day:2011-10-20_Cloud_SIG_Test_Day
  9. ↑ http://fedoraproject.org/wiki/QA/SOP_Test_Day_management
  10. ↑ http://fedoraproject.org/wiki/QA/Test_Days/Create

Fedora 16 preparation

As mentioned above, Fedora 16 release validation took up almost all of the QA team's time during the last few months, with very challenging Beta and Final releases. There were a total of 12 candidate builds for Beta and Final combined, and the whole team put in tireless work running the set of validation tests against each build and then investigating and verifying the large number of blocker bugs identified. The team was able to contribute to the release eventually going ahead with only a one week slip to the Beta schedule and no slip of the Final schedule, a considerable achievement in the light of the many complex changes in the Fedora 16 feature list.


Release criteria updates

Largely as a result of the Fedora 16 validation process, there were several adjustments and additions to the release criteria in recent weeks. After discussion of the proposed kickstart / unattended installation release criterion concluded, Adam Williamson reported that he had committed his proposed modifications[1]. He also committed a change to reflect the increased priority of EFI installations from Fedora 17 onwards[2].

Adam also passed on a suggestion from Peter Jones to improve the clarity of the virtualization criteria[3]. After an extensive discussion, an elegant wording suggestion from Albert Graham[4] was eventually accepted and committed[5].

Tim Flink raised the question to what extent support for Xen virtualization should be included in the release criteria[6]. After a similarly enthusiastic discussion, it was eventually agreed that Xen DomU support - effectively, the ability to install successfully as a Xen guest - should be a Final release criterion[7].

Adam also proposed downgrading some rarely-used kickstart deployment methods from Beta to Final in the criteria, requiring only the most commonly-used to be working at Beta stage[8].

Finally, Adam proposed a criterion for i18n (translation) issues[9]. After discussion, the proposal was agreed upon at a blocker review meeting later in the week[10].

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102599.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102600.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102601.html
  4. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102636.html
  5. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103680.html
  6. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/103127.html
  7. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103678.html
  8. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103557.html
  9. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103588.html
  10. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103679.html

Update policy changes

In September, Karsten Hopp raised the issue of a security update for Fedora 14 which had been languishing in the updates-testing repository for some time[1]. Adam Williamson explained that the amount of testers working on older releases was limited, and that the actual karma requirements for updates to be accepted were controlled by FESCo (the Fedora engineering steering committee), not the QA group[2]. Chuck Anderson noted that he had the update in question installed, but was struggling for lack of information on how to test it properly[3]. Rahul Sundaram suggested that Karsten file a ticket with FESCo to raise the issue[4], and Karsten did[5].

That ticket was merged with another similar one reported by Doug Ledford[6], which became a topic of concern to FESCo. After several rounds of discussions, FESCo first decided to relax the requirements for critical path updates somewhat by allowing them to be sent through to the stable repository without the 'required' karma after a period of two weeks had elapsed[7], and later proposed removing the requirement for critical path updates to receive positive karma from a proven tester[8], effectively a proposal to end the proven tester system, as this is the only function it serves.

The QA group discussed this proposal at the weekly meeting of 2011-11-07[9], agreeing that, while they had some reservations about the proposal, they were not definitely opposed to it, and recognized that critical path updates not receiving the currently-required karma is a significant problem.

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102493.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102497.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102503.html
  4. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102502.html
  5. ↑ http://fedorahosted.org/fesco/ticket/664
  6. ↑ http://fedorahosted.org/fesco/ticket/667
  7. ↑ http://fedorahosted.org/bodhi/ticket/642
  8. ↑ http://fedorahosted.org/fesco/ticket/667#comment:26
  9. ↑ http://fedoraproject.org/wiki/QA/Meetings/20111107

Update candidate notification

Samuel Greenfeld asked if there was any system to notify testers of new candidate updates for specific packages, and to determine what packages are being actively used on a system[1]. There were no takers for the second question, but for the first, Adam Williamson suggested using yum parameters that would allow one to specify only certain packages be pulled from the updates-testing repository[2], and Till Maas pointed out that Bodhi can actually provide per-package RSS notifications[3].

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102981.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102982.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102992.html

Proven tester meetings

As a response to the concerns about candidate updates not receiving enough karma, Kevin Fenzi ran a series of weekly proven tester meetups[1] from 2011-09-21 to 2011-10-26. Recaps of these meetings are available in the mailing list archives[2] [3] [4] [5] [6].

Kevin also proposed an updates-testing-info mailing list, containing only the mails about new packages in updates-testing[7]. However, the consensus was against the idea, as it was felt that it was easy enough to simply filter the desired mails from the test mailing list for those who did not want to read the other traffic.

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/102869.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/103000.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103341.html
  4. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103585.html
  5. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103840.html
  6. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/104043.html
  7. ↑ http://lists.fedoraproject.org/pipermail/test/2011-September/103163.html

QA group representation at FUDCon Pune

Ankur Sinha asked whether anyone from the QA team would be present at the upcoming FUDCon in Pune, India and able to do a presentation on the group's activities[1]. Adam Williamson replied that unfortunately none of the Red Hat team would be at the conference, but encouraged Ankur to take a shot at giving a presentation himself[2]. A S Alam then stepped up to volunteer to lead a QA session[3]. His session was scheduled for 2011-11-04[4], but we have no report on the event - if you were present, please write to the mailing list and let us know how it went!

  1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103712.html
  2. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103728.html
  3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-October/103739.html
  4. ↑ http://fudcon.in/sessions/fedora-testing
Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/QualityAssurance&oldid=261435"