[commits] [Wiki] changed: Doc/Dev/NewAppBestPracticesH6

[Ralf Lang (B1 Systems GmbH)]

rlang  Wed, 19 Sep 2018 07:10:12 +0000

Modified page: https://wiki.horde.org/Doc/Dev/NewAppBestPracticesH6
New Revision:  2
Change log:  Add testing

@@ -1,8 +1,15 @@
  + New App Design Proposals for H6

  This is, at least for now, a list of talking points, not a list of  
documented decisions or suggestions
  This is not about refactoring existing apps with thousands of LOCs  
but about understanding how to have a modern, lightweight start from  
scratch for new ideas.
+
+++ Quality
+Which commandline checks should any new app/code pass?  
horde-components qc (all or subset?)
+Which level of an app's architecture should strictly be covered by  
unit/integration tests?
+- All outgoing http requests (typical and known edge cases)
+- All entry points for incoming http requests (typical and known edge cases)
+- Any non-trivial actual computation/transformation of input data at  
library level (no need to test factored-out library code at app level  
though)

  ++ Server side Architecture

  +++ Inter-App and External Interfaces
@@ -30,5 +37,8 @@

  +++ JS Coding Standards
  Horde Coding standards currently include no guidance on how to  
format or structure js code of horde apps. Adopt some existing  
guideline?

+Which kind of UI testing or JS Unit Testing should be preferred?  
(type, mocha)?

++++ Default Development Platform
+Not to limit anybody or impose restriction, but there should be  
something to suggest for getting a new horde test system up on any  
laptop in 5 minutes or max 10 commandlines.