Testing instructions guide - Revision history

Devdocsbot: Protected "Testing instructions guide": Developer Docs Migration ([Edit=Allow only administrators] (indefinite))

2022-05-06T07:27:38Z

Protected "Testing instructions guide": Developer Docs Migration ([Edit=Allow only administrators] (indefinite))

← Older revision	Revision as of 07:27, 6 May 2022
(No difference)

Devdocsbot: Update migration status and path

2022-04-22T00:36:15Z

Update migration status and path

← Older revision		Revision as of 00:36, 22 April 2022
Line 1:		Line 1:
			{{Template:Migrated\|newDocId=/general/development/process/testing/guide}}
	This page has suggestions for developers on how to write good testing instructions for the weekly [[Testing of integrated issues\|testing of integrated issues]].		This page has suggestions for developers on how to write good testing instructions for the weekly [[Testing of integrated issues\|testing of integrated issues]].

Brendanheywood at 04:37, 18 November 2021

2021-11-18T04:37:27Z

← Older revision		Revision as of 04:37, 18 November 2021
Line 2:		Line 2:

	We recommend that you:		We recommend that you:

	# Number the steps in your test, and make use of sub-lists.		# Number the steps in your test, and make use of sub-lists.
	# Only put one action (preparation or validation) on each line - A step should only define a unique operation.		# Only put one action (preparation or validation) on each line - A step should only define a unique operation.
	# Promote test validations - Confirm, Verify or Ensure - should be in bold so that they are easily identifiable.		# Promote test validations - '''Confirm''', '''Verify''' or '''Ensure''' - should be in '''bold''' so that they are easily identifiable.
	# Make use of the [https://tracker.moodle.org/secure/WikiRendererHelpAction.jspa?section=all Jira Markdown formatting].		# Make use of the [https://tracker.moodle.org/secure/WikiRendererHelpAction.jspa?section=all Jira Markdown formatting].

	In addition, the following items may be included:		In addition, the following items may be included:

	# Setup requirements. If so, provide a link to the documentation e.g. https://docs.moodle.org/en/OAuth_2_services if necessary writing something in the dev docs.		# Setup requirements. If so, provide a link to the documentation e.g. https://docs.moodle.org/en/OAuth_2_services if necessary writing something in the dev docs.
	# Whether testing involves git/shell interaction, SQL operations... (commands in general), don't assume the tester knows how to perform that stuff. Instead, add them explicitly to the instructions.		# Whether testing involves git/shell interaction, SQL operations... (commands in general), don't assume the tester knows how to perform that stuff. Instead, add them explicitly to the instructions.
Line 16:		Line 13:
	# Whether more than one browser should be used. (Tester should specify which browsers they used.)		# Whether more than one browser should be used. (Tester should specify which browsers they used.)
	# Whether extra testing around the issue is required.		# Whether extra testing around the issue is required.

	[[Category: Processes]]		[[Category: Processes]]

Stronk7: one action per step

2019-09-04T13:42:41Z

one action per step

← Older revision		Revision as of 13:42, 4 September 2019
Line 4:		Line 4:

	# Number the steps in your test, and make use of sub-lists.		# Number the steps in your test, and make use of sub-lists.
			# Only put one action (preparation or validation) on each line - A step should only define a unique operation.
	# Promote test validations - Confirm, Verify or Ensure - should be in bold so that they are easily identifiable.		# Promote test validations - Confirm, Verify or Ensure - should be in bold so that they are easily identifiable.
	~~# Only put one test validation on each line - A test step should only have one test validation at a time.~~
	# Make use of the [https://tracker.moodle.org/secure/WikiRendererHelpAction.jspa?section=all Jira Markdown formatting].		# Make use of the [https://tracker.moodle.org/secure/WikiRendererHelpAction.jspa?section=all Jira Markdown formatting].

Stronk7: Remove wip and add point about adding commands (git, sql...) to the testing instructions. Signed by iTeam.

2019-09-03T17:12:51Z

Remove wip and add point about adding commands (git, sql...) to the testing instructions. Signed by iTeam.

← Older revision		Revision as of 17:12, 3 September 2019
Line 1:		Line 1:
	~~{{Work in progress~~
	~~\|forumurl = https://moodle.org/mod/forum/view.php?id=55~~
	~~\|info =~~
	}}
	This page has suggestions for developers on how to write good testing instructions for the weekly [[Testing of integrated issues\|testing of integrated issues]].		This page has suggestions for developers on how to write good testing instructions for the weekly [[Testing of integrated issues\|testing of integrated issues]].

Line 15:		Line 11:

	# Setup requirements. If so, provide a link to the documentation e.g. https://docs.moodle.org/en/OAuth_2_services if necessary writing something in the dev docs.		# Setup requirements. If so, provide a link to the documentation e.g. https://docs.moodle.org/en/OAuth_2_services if necessary writing something in the dev docs.
			# Whether testing involves git/shell interaction, SQL operations... (commands in general), don't assume the tester knows how to perform that stuff. Instead, add them explicitly to the instructions.
	# Whether testing may be done using the [https://qa.moodle.net/ Moodle QA testing site].		# Whether testing may be done using the [https://qa.moodle.net/ Moodle QA testing site].
	# Whether multiple themes {{Template:CurrentlySupportedThemes}} should be used.		# Whether multiple themes {{Template:CurrentlySupportedThemes}} should be used.

Stronk7: Modified to apply the {{Template:CurrentlySupportedThemes}}

2019-03-07T11:35:22Z

Modified to apply the {{Template:CurrentlySupportedThemes}}

← Older revision		Revision as of 11:35, 7 March 2019
Line 16:		Line 16:
	# Setup requirements. If so, provide a link to the documentation e.g. https://docs.moodle.org/en/OAuth_2_services if necessary writing something in the dev docs.		# Setup requirements. If so, provide a link to the documentation e.g. https://docs.moodle.org/en/OAuth_2_services if necessary writing something in the dev docs.
	# Whether testing may be done using the [https://qa.moodle.net/ Moodle QA testing site].		# Whether testing may be done using the [https://qa.moodle.net/ Moodle QA testing site].
	# Whether ~~the Boost and / or Clean theme~~ should be used.		# Whether multiple themes {{Template:CurrentlySupportedThemes}} should be used.
	# Whether more than one browser should be used. (Tester should specify which browsers they used.)		# Whether more than one browser should be used. (Tester should specify which browsers they used.)
	# Whether extra testing around the issue is required.		# Whether extra testing around the issue is required.

	[[Category: Processes]]		[[Category: Processes]]

Andrewnicols: Make the list a little clearer, and add a link to Jira markdown formatting.

2018-03-26T01:46:24Z

Make the list a little clearer, and add a link to Jira markdown formatting.

← Older revision		Revision as of 01:46, 26 March 2018
Line 5:		Line 5:
	This page has suggestions for developers on how to write good testing instructions for the weekly [[Testing of integrated issues\|testing of integrated issues]].		This page has suggestions for developers on how to write good testing instructions for the weekly [[Testing of integrated issues\|testing of integrated issues]].

	# Number the test ~~steps~~.		We recommend that you:
	# ~~Test~~ validations - Confirm, Verify or Ensure - should be in bold.
	# A test step should only have one test validation.		# Number the steps in your test, and make use of sub-lists.
			# Promote test validations - Confirm, Verify or Ensure - should be in bold so that they are easily identifiable.
			# Only put one test validation on each line - A test step should only have one test validation at a time.
			# Make use of the [https://tracker.moodle.org/secure/WikiRendererHelpAction.jspa?section=all Jira Markdown formatting].

	In addition, the following items may be included:		In addition, the following items may be included:

Tsala: rewording

2017-09-28T13:47:38Z

rewording

← Older revision		Revision as of 13:47, 28 September 2017
Line 5:		Line 5:
	This page has suggestions for developers on how to write good testing instructions for the weekly [[Testing of integrated issues\|testing of integrated issues]].		This page has suggestions for developers on how to write good testing instructions for the weekly [[Testing of integrated issues\|testing of integrated issues]].

	~~In addition to numbered~~ test steps, ~~the following items may~~ be ~~included:~~		# Number the test steps.
			# Test validations - Confirm, Verify or Ensure - should be in bold.
			# A test step should only have one test validation.

	[] Setup requirements? If so, provide a link to the documentation e.g. https://docs.moodle.org/en/OAuth_2_services if necessary writing something in the dev docs.		In addition, the following items may be included:
	~~[] Testing~~ may be done using the [https://qa.moodle.net/ Moodle QA testing site]?
	~~[] Testing must be done using~~ Boost and / or Clean theme?		# Setup requirements. If so, provide a link to the documentation e.g. https://docs.moodle.org/en/OAuth_2_services if necessary writing something in the dev docs.
	~~[] Testing must be done using~~ more than one browser? (Tester should specify which browsers they used.)		# Whether testing may be done using the [https://qa.moodle.net/ Moodle QA testing site].
	~~[] Extra~~ testing around the issue is required?		# Whether the Boost and / or Clean theme should be used.
			# Whether more than one browser should be used. (Tester should specify which browsers they used.)
			# Whether extra testing around the issue is required.

	[[Category: Processes]]~~weekl~~		[[Category: Processes]]

Tsala: work in progress template, items for inclusion, category

2017-09-26T10:19:05Z

work in progress template, items for inclusion, category

New page

{{Work in progress
|forumurl = https://moodle.org/mod/forum/view.php?id=55
|info =
}}
This page has suggestions for developers on how to write good testing instructions for the weekly [[Testing of integrated issues|testing of integrated issues]].

In addition to numbered test steps, the following items may be included:

[] Setup requirements? If so, provide a link to the documentation e.g. https://docs.moodle.org/en/OAuth_2_services if necessary writing something in the dev docs.
[] Testing may be done using the [https://qa.moodle.net/ Moodle QA testing site]?
[] Testing must be done using Boost and / or Clean theme?
[] Testing must be done using more than one browser? (Tester should specify which browsers they used.)
[] Extra testing around the issue is required?

[[Category: Processes]]weekl