Integrics Wiki - Recent changes [en-gb]

Coding Guidelines

Vlasis — Thu, 03 Sep 2026 19:49:15 GMT

← Older revision		Revision as of 19:49, 3 September 2026
Line 42:		Line 42:
	** Use the "<condition> ? <if true> : <if false>" construct if thought appropriate.		** Use the "<condition> ? <if true> : <if false>" construct if thought appropriate.
	** For Enswitch versions 4.2 and newer prefer the array style syntax for SQL queries even for data with a single parameter, e.g. data => [ $a->{ 'uniqueid' } ].		** For Enswitch versions 4.2 and newer prefer the array style syntax for SQL queries even for data with a single parameter, e.g. data => [ $a->{ 'uniqueid' } ].
			** Use POSIX::_exit() instead of exit() in Enswitch versions up to 4.3.
			** Use smart_exit() from lib/Utilities.pm instead of exit() in Enswitch versions 4.4+.

	* Databases		* Databases

Developer testing policy

Dcunningham — Tue, 25 Aug 2026 12:19:07 GMT

← Older revision		Revision as of 12:19, 25 August 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	Integrics policy for testing of code is as follows.		Integrics policy for testing of code is as follows.

	For development of new features, the code must be tested by:		For development of new features, the code must be tested by both:
	# ~~Firstly by~~ AI such as Claude or ChatGPT.		# AI such as Claude or ChatGPT.
	# ~~Secondly by another~~ engineer.		# Another engineer.

	For fixes to existing features, the code must be tested by:		For fixes to existing features, the code must be tested by:
	# AI such as Claude or ChatGPT, or another engineer if that's not possible.		# AI such as Claude or ChatGPT, or another engineer if that's not possible.
			# Full testing of the change on the version the problem was reported on, and basic testing of all other versions affected.

Developer testing policy

Dcunningham — Fri, 21 Aug 2026 12:03:52 GMT

Created page with "Integrics policy for testing of code is as follows. For development of new features, the code must be tested by: # Firstly by AI such as Claude or ChatGPT. # Secondly by another engineer. For fixes to existing features, the code must be tested by: # AI such as Claude or ChatGPT, or another engineer if that's not possible."

New page

Integrics policy for testing of code is as follows.

For development of new features, the code must be tested by:
# Firstly by AI such as Claude or ChatGPT.
# Secondly by another engineer.

For fixes to existing features, the code must be tested by:
# AI such as Claude or ChatGPT, or another engineer if that's not possible.