🇮🇷 Iran Proxy | https://www.wikipedia.org/wiki/Template:Talk_header/testcases4
Jump to content

Template:Talk header/testcases4

From Wikipedia, the free encyclopedia

Automatic archive bot parameter detection with human readable durations

[edit]

These tests verify that correct value are supplied when a validly formatted Miszabot/config exists for the page. The template can determine all four values if present in the config, and uses them to automatically populate information about automatic archiving. Durations are displayed in a human-readable format in the direct text of the page, and the actual value set in the config is displayed in a tooltip (e.g. "3 years" in the text, "26000 hours" in the tooltip).

Alternatively, run the following tests setting the Context title to each Talk page in turn in the numbered tests below, after having pasted the following code (once) into the Input field at Special:ExpandTemplates:

Tests for pages using Miszabot config:

  • Test A–1: Talk:Algeria – expect "3 months" in-text; the tooltip reads "Lowercase sigmabot III ... 90 days ... more than 4 threads are present"
  • Test A–2: Talk:France – expect 3 months / Lowercase sigmabot III – 90 days – minthreads = 4
  • Test A–3: Talk:Muammar Gaddafi – expect 2 months / Lowercase sigmabot III – 60 days
  • Test A–4: Talk:Physics – expect 3 months / Lowercase sigmabot III – 100 days – minthreads=4
  • Test A–5: Talk:Noam Chomsky – expect 45 days / Lowercase sigmabot III – minthreads=3
  • Test A–5: Talk:Mustang – expect 2 months / Lowercase sigmabot III – 61 days
  • Test A–6: Talk:-ism – expect 3 years / Lowercase sigmabot III – 1095 days – minthreads=1

Tests for pages using User:ClueBot III/ArchiveThis

  • Test B–2: Talk:The Exorcist – expect 30 days / Cluebot III – 720 hours – minthreads = 4
  • Test B–3: Talk:List of colors – expect 7.5 days / Cluebot III – 183 hours – minthreads = 4
  • Test B–4: Talk:Toronto – expect 2 months / Cluebot III – 1440 hours
  • Test B–5: Talk:Website – expect 3 months / Cluebot III – 2160 hours – minthreads = 5
  • Test B–6: Talk:Switzerland – expect 4 months / Cluebot III – 2880 hours – minthreads = 5
  • Test B–7: Talk:Fake news – expect 3 months / Cluebot III – 2160 hours – minthreads = 4
  • Test B–8: Talk:Spotify – expect 3 months / Cluebot III – 2160 hours – minthreads = 4
  • Test B–9: Talk:2022 – expect 30 days / Cluebot III – 720 hours – minthreads = 10
  • Test B–10: Talk:Macedonia – expect 3 months / Cluebot III – 2160 hours – minthreads = 4

The subtemplate Template:Talk header/archivebotparse can be tested directly, using the two-param method, passing the name of the Talk page in param 2. These tests follow:

Tests for Talk pages that use User:MiszaBot/config

[edit]

Tests for Talk pages that use User:ClueBot III/ArchiveThis

[edit]

More like these: Advanced search.

Testing upgrade for minimum threads to archive

[edit]

Talk pages that use Miszabot config

[edit]

Find MiszaBot-config archiving test cases:
hastemplate:"talk header" hastemplate:"User:MiszaBot/config" insource:"minthreadstoarchive=" -insource:"archive_age=" -insource:"bot="

Talk pages that use Cluebot

[edit]

Find Cluebot archiving test cases:
hastemplate:"talk header" hastemplate:"User:ClueBot III/ArchiveThis" insource:"minarchthreads=" -insource:"archive_age=" -insource:"bot="

These can be tested using Special:ExpandTemplates as explained in section 1. A. How to test above. Another way, is to click the top link in the 1.A § Examples section (Test 1. Talk:France), and then replace the context title at the top with the Talk pages listed in the test set above, and re-execute the test for each one.

Testing human readable time units

[edit]

This section is about testing the display of time units in the archiving bot notice. This notice appears just above the 'Search archives' input box, and may read something like, Auto-archiving period: 30 days. The value '30 days'k ultimately comes from the archiving bot configuration on the Talk page, however, users have a choice of what units they wish to use, such as, 1 month, 30 days, 4 weeks, or even .0833 year.

Template {{human readable duration}} is responsible for generating the appropriate display value, and details of its functionality can be viewed there. The first step in testing this feature here, is to review the test cases there. Assuming they all pass, then spot-check a few cases here.

In situ test – find a test case from the search links or the lists, and do a pair of tests, comparing live and sandbox:

  • live: check the value given for the archiving period in the Talk header template, and compare to the expected value (if from the lists below) or compare to the expected value (as calculated at {{human readable duration}}).
  • sandbox: edit the talk page, append /sandbox after the {{Talk header invocation, and click the Show preview button. Then check the value as for the live example. Test passes, if the sandbox value = live value (except for initial version, when sandbox value will be accurate, and live will have the unfriendly value straight out of the config).

Miszabot configs with a 'days' period of 3 digits or more

[edit]

To find Miszabot configs with a 'days' period of 3 digits or more on pages having a Talk header, use this search. Examples:

  1. Talk:Avicenna = 900d ⟶ 2.5 years
  2. Talk:Cascadia movement = 1826d ⟶ 5 years
  3. Talk:Criticism of the BBC = 100d ⟶ 3 months
  4. Talk:David (Michelangelo) = 3650d
  5. Talk:Grey's Anatomy = 730d ⟶ 2 years
  6. Talk:Iraq War = 183d ⟶ 6 months
  7. Talk:Kim Kardashian = 1031d ⟶ 3 years
  8. Talk:Liberty University = 365d
  9. Talk:Ronda Rousey = 9000d ⟶ 24.5 years
  10. Talk:Secondary school = 1095d ⟶ 3 years
  11. Talk:T-34 = 5090d ⟶ 14 years
  12. Talk:Shrek the Third = 5110d ⟶ 14 years
  13. Talk:The Lost Tomb of Jesus = 36502d (no human readable given; no archives present; archiving text detail appears in plain view instead of in hover text)
  • Miszabot config only uses days; other values are invalid, but this search will find them (17, as of Nov. 2024) all fixed.

Cluebot III configs

[edit]

Cluebot uses the age parameter, which is denominated in hours. Here are some handy conversions to hours, for use in searching for Talk pages with a specified range:

  • 7d=168h; 30d=5040h; 120d=20160h; 122d=20496h; 180d=30240h; 183d=31744h; 365d=61320h; 730d=122640; 3y=183960; 5y=306600; 10y=613200

Searches for Talk pages having Cluebot archive configs with param |age= in selected ranges (denominated here in days for convenience; bot config is in hours only):

Run in situ tests for Talk pages with Cluebot configs the same way as for Miszabot configs.

Examples:

  1. Talk:Amritpal Singh 48/2 days/2 days
  2. Talk:Murder of Laci Peterson 90/4/4
  3. Talk:2023 Monterey Park shooting 168/7/7
  4. Talk:2018 Pakistani general election 720/30/30
  5. Talk:Hot air balloon 2160/90/3 months

Testing categorization of pages using deprecated archiving parameters

[edit]

The update to the template to automate detection of archive bot parameters (see tests for #Automatic archive bot parameter detection above) opened the possibility of removing the bot display parameters |age=, |units=, |bot=, and |minthreadsleft=, which were formerly used for this purpose, and were deprecated in rev. 1223139724 of 10 May 2024.

Background

[edit]

Testing

[edit]

The deprecated parameters which should cause categorization are: archive_age, archive_bot, archive_units, minthreadsleft, age, bot, and units.

Tests may be run either Special:ExpandTemplates, or in situ.

Testing involves checking whether talk header templates using any of the four deprecated archive bot parameters cause the page to be categorized properly into the category Category:Pages using Talk header with deprecated parameters. Categories are not displayed on this page, so testing cannot not take place here; rather, it can be done in situ or via Special:ExpandTemplates. For general considerations about this type of testing, please see section § Automatic archive bot parameter detection above, subsections § A. Testing with ExpandTemplates, and § C. Testing in situ.

Via Special:ExpandTemplates

[edit]

In situ tests

[edit]

A successful in situ test is one which shows the following at the bottom of the page in Preview mode, always for the Sandbox test, and also for the Live test in subsequent releases:

If you see the above message, the test has passed.

Detection of deprecated parameters removed from valid param check

[edit]
Test archive_age
{{Talk header|archive_age=12}}
Side by side comparison
{{Talk header}}{{Talk header/sandbox}}