DB layer 2.0 functional testing - Revision history

Sarjona at 08:10, 10 February 2025

2025-02-10T08:10:27Z

← Older revision		Revision as of 08:10, 10 February 2025
Line 1:		Line 1:
			{{Template:WillNotMigrate}}

	{{Template:Development:dmllib 2.0}}{{Moodle_2.0}}		{{Template:Development:dmllib 2.0}}{{Moodle_2.0}}

Mudrd8mz: Text replacement - "`" to ""`


2021-07-14T13:32:37Z
Text replacement - "<code php>" to "<syntaxhighlight lang="php">"

				
				
				
				
				
				← Older revision
				Revision as of 13:32, 14 July 2021
				
Line 9:
Line 9:



You can test current database specified in config.php, you can also specify other DB servers via following config.php settings, for example: You can test current database specified in config.php, you can also specify other DB servers via following config.php settings, for example:
<code php> <syntaxhighlight lang="php">
$CFG->func_test_db_1 = array("native", "mysqli", "localhost", "root", "yourpassword", "moodle", "tst_", array('dbengine'=>'InnoDB')); $CFG->func_test_db_1 = array("native", "mysqli", "localhost", "root", "yourpassword", "moodle", "tst_", array('dbengine'=>'InnoDB'));
$CFG->func_test_db_2 = array("native", "mysqli", "localhost", "root", "yourpassword", "moodle2", "tst_", array('dbengine'=>'MyISAM')); $CFG->func_test_db_2 = array("native", "mysqli", "localhost", "root", "yourpassword", "moodle2", "tst_", array('dbengine'=>'MyISAM'));

`Mudrd8mz: Text replacement - "`" to ""

2021-07-14T13:05:31Z

Text replacement - "</code>" to "</syntaxhighlight>"

← Older revision		Revision as of 13:05, 14 July 2021
Line 14:		Line 14:
	$CFG->func_test_db_3 = array("native", "pgsql", "localhost", "moodleuser", "yourpassword", "moodle2", "tst_", NULL);		$CFG->func_test_db_3 = array("native", "pgsql", "localhost", "moodleuser", "yourpassword", "moodle2", "tst_", NULL);
	$CFG->func_test_db_4 = array("native", "mssql", "192.168.15.41", "sa", "yourpassword", "moodle", "tst_", NULL);		$CFG->func_test_db_4 = array("native", "mssql", "192.168.15.41", "sa", "yourpassword", "moodle", "tst_", NULL);
	</~~code~~>		</syntaxhighlight>

	== DDL tests ==		== DDL tests ==

Skodak at 18:45, 3 September 2010

2010-09-03T18:45:20Z

← Older revision		Revision as of 18:45, 3 September 2010
Line 1:		Line 1:
	{{{Template:Development:dmllib 2.0}}{{Moodle_2.0}}		{{Template:Development:dmllib 2.0}}{{Moodle_2.0}}

	Functional unit tests can be used to test the interaction of Moodle and database, it is testing following:		Functional unit tests can be used to test the interaction of Moodle and database, it is testing following:

Skodak at 18:44, 3 September 2010

2010-09-03T18:44:44Z

@@ Line 1: / Line 1: @@
-{{Work in progress}}{{Template:Development:dmllib 2.0}}{{Moodle_2.0}}== DDL tests ==
+{{{Template:Development:dmllib 2.0}}{{Moodle_2.0}}
-* create_table
+Functional unit tests can be used to test the interaction of Moodle and database, it is testing following:
-* drop_table
+* SQL database server
-* add_enum_field
+* PHP database driver
-* add_numeric_field
+* Moodle DB connection settings, driver configuration and server settings
-* drop_field
+* Moodle DDL generator
-* change_field_type
+* Moodle DML driver
-== DML tests ==
+You can test current database specified in config.php, you can also specify other DB servers via following config.php settings, for example:
-The following methods have been implemented in unit tests:
+<code php>
-* fix_sql_params
+== DDL tests ==
-* get_tables
+All DDL test must pass on any production server.
-== Still to do ==
+== DML tests ==
+Ideally all DML tests should pass on production servers.
-* How do these methods behave when given invalid params?
+Common problems:
-* Are exceptions in place, and are they caught appropriately?
+* MySQL MyISAM engine does ACID compliant and does not support transactions, please consider upgrading to InnoDB.

Stronk7: find_sequence_name() out in Moodle 2.0

2009-10-11T21:54:20Z

find_sequence_name() out in Moodle 2.0

← Older revision		Revision as of 21:54, 11 October 2009
Line 32:		Line 32:
	* check_constraint_exists		* check_constraint_exists
	* find_key_name		* find_key_name
	* find_sequence_name
	* delete_tables_from_xmldb_file		* delete_tables_from_xmldb_file
	* install_from_xmldb_file		* install_from_xmldb_file

Stronk7: added correct menu template

2009-05-05T15:19:20Z

added correct menu template

← Older revision		Revision as of 15:19, 5 May 2009
Line 1:		Line 1:
	{{Work in progress}}{{Moodle_2.0}}== DDL tests ==		{{Work in progress}}{{Template:Development:dmllib 2.0}}{{Moodle_2.0}}== DDL tests ==
	Based on tests already used in xmldb, the following methods have been implemented in simpletest:		Based on tests already used in xmldb, the following methods have been implemented in simpletest:

Stronk7: delete included page

2009-05-05T15:18:19Z

delete included page

← Older revision		Revision as of 15:18, 5 May 2009
Line 1:		Line 1:
	{{Work in progress~~}}{{Development:dmllib 2.0~~}}{{Moodle_2.0}}== DDL tests ==		{{Work in progress}}{{Moodle_2.0}}== DDL tests ==
	Based on tests already used in xmldb, the following methods have been implemented in simpletest:		Based on tests already used in xmldb, the following methods have been implemented in simpletest:

Stronk7 at 17:50, 9 November 2008

2008-11-09T17:50:42Z

← Older revision		Revision as of 17:50, 9 November 2008
Line 1:		Line 1:
	{{Work in progress}}{{~~Template:~~Development:dmllib 2.0}}{{Moodle_2.0}}== DDL tests ==		{{Work in progress}}{{Development:dmllib 2.0}}{{Moodle_2.0}}== DDL tests ==
	Based on tests already used in xmldb, the following methods have been implemented in simpletest:		Based on tests already used in xmldb, the following methods have been implemented in simpletest:

Stronk7: dmllib 2.0 functional testing moved to DB layer 2.0 functional testing

2008-07-25T17:14:24Z

dmllib 2.0 functional testing moved to DB layer 2.0 functional testing

← Older revision	Revision as of 17:14, 25 July 2008
(No difference)

← Older revision		Revision as of 13:32, 14 July 2021
Line 9:		Line 9:

	You can test current database specified in config.php, you can also specify other DB servers via following config.php settings, for example:		You can test current database specified in config.php, you can also specify other DB servers via following config.php settings, for example:
	<~~code~~ php>		<syntaxhighlight lang="php">
	$CFG->func_test_db_1 = array("native", "mysqli", "localhost", "root", "yourpassword", "moodle", "tst_", array('dbengine'=>'InnoDB'));		$CFG->func_test_db_1 = array("native", "mysqli", "localhost", "root", "yourpassword", "moodle", "tst_", array('dbengine'=>'InnoDB'));
	$CFG->func_test_db_2 = array("native", "mysqli", "localhost", "root", "yourpassword", "moodle2", "tst_", array('dbengine'=>'MyISAM'));		$CFG->func_test_db_2 = array("native", "mysqli", "localhost", "root", "yourpassword", "moodle2", "tst_", array('dbengine'=>'MyISAM'));