Testing of new modules - Revision history

David Haslam: /* Lexicons */ Category:Testing

2010-12-09T20:11:09Z

‎Lexicons: Category:Testing

David Haslam: /* All modules */ If you suspect a module bug, please take note of the advice in DevTools:Modules#Debugging_modules.

2010-10-16T18:08:21Z

‎All modules: If you suspect a module bug, please take note of the advice in DevTools:Modules#Debugging_modules.

David Haslam: /* Lexicons */ Category:Modules

2009-12-04T10:32:40Z

‎Lexicons: Category:Modules

David Haslam: /* Lexicons */ Category:Module

2009-12-04T10:32:26Z

‎Lexicons: Category:Module

David Haslam: /* Lexicons */ hyphen

2009-10-20T14:30:18Z

‎Lexicons: hyphen

David Haslam: /* Genbooks */ hyphens

2009-10-20T14:29:58Z

‎Genbooks: hyphens

David Haslam: /* All modules */ hyphens

2009-10-20T14:29:38Z

‎All modules: hyphens

Eelik: /* Bibles */

2008-06-17T05:00:04Z

‎Bibles

Refdoc at 21:14, 6 June 2008

2008-06-06T21:14:22Z

Eelik at 15:25, 6 June 2008

2008-06-06T15:25:38Z

← Older revision		Revision as of 20:11, 9 December 2010
Line 26:		Line 26:

	[[Category:Modules]]		[[Category:Modules]]
		+	[[Category:Testing]]

← Older revision		Revision as of 18:08, 16 October 2010
Line 9:		Line 9:

	Try to find a piece of text for each feature. Does it work with all front-ends which support that feature?		Try to find a piece of text for each feature. Does it work with all front-ends which support that feature?
		+
		+	If you suspect a module bug, please take note of the advice in [[DevTools:Modules#Debugging_modules]].

	==Bibles==		==Bibles==

← Older revision		Revision as of 10:32, 4 December 2009
Line 23:		Line 23:
	Try to access the first and the last entry. If a front-end offers more than one way to move between the entries try all of them. Broken modules may have for example infinite loops.		Try to access the first and the last entry. If a front-end offers more than one way to move between the entries try all of them. Broken modules may have for example infinite loops.

−	[[Category:~~Module~~]]	+	[[Category:Modules]]

← Older revision		Revision as of 10:32, 4 December 2009
Line 22:		Line 22:
	==Lexicons==		==Lexicons==
	Try to access the first and the last entry. If a front-end offers more than one way to move between the entries try all of them. Broken modules may have for example infinite loops.		Try to access the first and the last entry. If a front-end offers more than one way to move between the entries try all of them. Broken modules may have for example infinite loops.
		+
		+	[[Category:Module]]

← Older revision		Revision as of 14:30, 20 October 2009
Line 21:		Line 21:

	==Lexicons==		==Lexicons==
−	Try to access the first and the last entry. If a ~~frontend~~ offers more than one way to move between the entries try all of them. Broken modules may have for example infinite loops.	+	Try to access the first and the last entry. If a front-end offers more than one way to move between the entries try all of them. Broken modules may have for example infinite loops.

@@ Line 18: / Line 18: @@
 ==Genbooks==
-Try to navigate in the tree structure. Try to find a more "original" source text or some other source from which you can see what the book should contain. Comparing several frontends is helpful. For example there have been problems with certain modules when some frontends try to get the key list in certain way. Some frontends may fail there while others succeed.
+Try to navigate in the tree structure. Try to find a more "original" source text or some other source from which you can see what the book should contain. Comparing several front-ends is helpful. For example there have been problems with certain modules when some front-ends try to get the key list in certain way. Some front-ends may fail there while others succeed.
 ==Lexicons==
 Try to access the first and the last entry. If a frontend offers more than one way to move between the entries try all of them. Broken modules may have for example infinite loops.

@@ Line 6: / Line 6: @@
 Conf file should be encoded correctly with the same encoding as the module. "About" section should not have formatting or tags which are not mentioned in the [[DevTools:Modules#Creating_a_.conf_File|.conf wiki section]].
-All features should be listed in the conf file of the module. If not, all frontends can't use the features. (TODO: how to know what the features should be?)
+All features should be listed in the conf file of the module. If not, all front-ends can't use the features. (TODO: how to know what the features should be?)
-Try to find a piece of text for each feature. Does it work with all frontends which support that feature?
+Try to find a piece of text for each feature. Does it work with all front-ends which support that feature?
 ==Bibles==

← Older revision		Revision as of 05:00, 17 June 2008
Line 14:		Line 14:

	Select some random verses from each book and see if they are correct.		Select some random verses from each book and see if they are correct.
		+
		+	If you find a missing verse go back in the module to see if a verse or a bunch of verses has been moved to the end of the previous verse. In this case the original text had a different versification scheme than the KJV one we use ATM. It would be a good practice to notify this in the conf file "About" section.

	==Genbooks==		==Genbooks==

← Older revision		Revision as of 21:14, 6 June 2008
Line 1:		Line 1:
	This is a new page. We should have some common criteria which we put down to testing a module.		This is a new page. We should have some common criteria which we put down to testing a module.
		+
		+	All modules listed on [[Modules in the beta repository]] will require testing.

	==All modules==		==All modules==

← Older revision		Revision as of 15:25, 6 June 2008
Line 1:		Line 1:
	This is a new page. We should have some common criteria which we put down to testing a module.		This is a new page. We should have some common criteria which we put down to testing a module.
		+
		+	==All modules==
		+	Conf file should be encoded correctly with the same encoding as the module. "About" section should not have formatting or tags which are not mentioned in the [[DevTools:Modules#Creating_a_.conf_File\|.conf wiki section]].
		+
		+	All features should be listed in the conf file of the module. If not, all frontends can't use the features. (TODO: how to know what the features should be?)
		+
		+	Try to find a piece of text for each feature. Does it work with all frontends which support that feature?
		+
		+	==Bibles==
		+	Open the first and the last verse of each book. (TODO: list of books and their last chapter:verse?) Compare them to a module you know is correct to see if they have the correct text (if you know or at least can guess the words of the language).
		+
		+	Select some random verses from each book and see if they are correct.
		+
		+	==Genbooks==
		+	Try to navigate in the tree structure. Try to find a more "original" source text or some other source from which you can see what the book should contain. Comparing several frontends is helpful. For example there have been problems with certain modules when some frontends try to get the key list in certain way. Some frontends may fail there while others succeed.
		+
		+	==Lexicons==
		+	Try to access the first and the last entry. If a frontend offers more than one way to move between the entries try all of them. Broken modules may have for example infinite loops.