stoney core: Requirements - Revision history

Tiziano at 12:56, 16 April 2014

2014-04-16T12:56:49Z

← Older revision		Revision as of 14:56, 16 April 2014
Line 21:		Line 21:
	** Use one of the following options for the REST API Testing (& documentation):		** Use one of the following options for the REST API Testing (& documentation):
	*** [http://frisbyjs.com/ Frisby], partially uses Jasmine and integrates via JUnit XML output with Jenkins		*** [http://frisbyjs.com/ Frisby], partially uses Jasmine and integrates via JUnit XML output with Jenkins
			**** Has integrated JSON Schema Testing!
	*** [https://github.com/apiaryio/dredd Dredd]+[http://apiblueprint.org/ apiblueprint] (perhaps directly via the webservice at http://apiary.io/) which makes it possible to keep specification, documentation and example in one place and test the REST API against the specification and use the examples as test cases.		*** [https://github.com/apiaryio/dredd Dredd]+[http://apiblueprint.org/ apiblueprint] (perhaps directly via the webservice at http://apiary.io/) which makes it possible to keep specification, documentation and example in one place and test the REST API against the specification and use the examples as test cases.
	*** [http://developers.helloreverb.com/swagger/ Swagger]		*** [http://developers.helloreverb.com/swagger/ Swagger]

Michael at 09:21, 30 January 2014

2014-01-30T09:21:49Z

← Older revision		Revision as of 11:21, 30 January 2014
Line 23:		Line 23:
	*** [https://github.com/apiaryio/dredd Dredd]+[http://apiblueprint.org/ apiblueprint] (perhaps directly via the webservice at http://apiary.io/) which makes it possible to keep specification, documentation and example in one place and test the REST API against the specification and use the examples as test cases.		*** [https://github.com/apiaryio/dredd Dredd]+[http://apiblueprint.org/ apiblueprint] (perhaps directly via the webservice at http://apiary.io/) which makes it possible to keep specification, documentation and example in one place and test the REST API against the specification and use the examples as test cases.
	*** [http://developers.helloreverb.com/swagger/ Swagger]		*** [http://developers.helloreverb.com/swagger/ Swagger]
	*** [~~https~~://~~github~~.~~com~~/~~mashery/iodocs I/O Docs~~]		*** [http://json-schema.org/ JSON Schema]
	** Use static mock json objects under different URLs to provide mock server-side data for testing the webfrontend		** Use static mock json objects under different URLs to provide mock server-side data for testing the webfrontend

Tiziano at 09:13, 12 January 2014

2014-01-12T09:13:35Z

← Older revision		Revision as of 11:13, 12 January 2014
Line 13:		Line 13:
	* Use HTML5 and not HTML 4.01, not transitional, not XHTML		* Use HTML5 and not HTML 4.01, not transitional, not XHTML
	** Use [http://getbootstrap.com/ bootstrap] (version 3) resp. [http://angular-ui.github.io/bootstrap/ AngularUI-Bootstrap] to get a working pre-defined environment including compat-shims for IE, etc.		** Use [http://getbootstrap.com/ bootstrap] (version 3) resp. [http://angular-ui.github.io/bootstrap/ AngularUI-Bootstrap] to get a working pre-defined environment including compat-shims for IE, etc.
			* Translation:
			** http://pascalprecht.github.io/angular-translate/
	* Testing		* Testing
	** Use [http://pivotal.github.io/jasmine/ Jasmine] for JavaScript testing		** Use [http://pivotal.github.io/jasmine/ Jasmine] for JavaScript testing

Tiziano at 11:28, 7 January 2014

2014-01-07T11:28:22Z

← Older revision		Revision as of 13:28, 7 January 2014
Line 5:		Line 5:
	*** Add [https://github.com/mgonto/restangular Restangular] to make it even easier to connect to the REST-API, see also this [http://stackoverflow.com/questions/16394089/how-to-access-the-services-from-restful-api-in-my-angularjs-page answer on stackoverflow]		*** Add [https://github.com/mgonto/restangular Restangular] to make it even easier to connect to the REST-API, see also this [http://stackoverflow.com/questions/16394089/how-to-access-the-services-from-restful-api-in-my-angularjs-page answer on stackoverflow]
	*** From [http://angular-ui.github.io/bootstrap/ angular-ui] use:		*** From [http://angular-ui.github.io/bootstrap/ angular-ui] use:
	**** [http://angular-ui.github.io/bootstrap/ UI-Bootstrap] to integrate with Bootstrap ~~(note: you have to use bootstrap3 branch for now)~~		**** [http://angular-ui.github.io/bootstrap/ UI-Bootstrap] to integrate with Bootstrap 3
	**** [http://angular-ui.github.io/ui-utils/ UI-Utils] as needed		**** [http://angular-ui.github.io/ui-utils/ UI-Utils] as needed
	**** [https://github.com/angular-ui/ui-router UI-router] as needed		**** [https://github.com/angular-ui/ui-router UI-router] as needed

Tiziano at 16:59, 3 January 2014

2014-01-03T16:59:09Z

← Older revision		Revision as of 18:59, 3 January 2014
Line 21:		Line 21:
	*** [http://frisbyjs.com/ Frisby], partially uses Jasmine and integrates via JUnit XML output with Jenkins		*** [http://frisbyjs.com/ Frisby], partially uses Jasmine and integrates via JUnit XML output with Jenkins
	*** [https://github.com/apiaryio/dredd Dredd]+[http://apiblueprint.org/ apiblueprint] (perhaps directly via the webservice at http://apiary.io/) which makes it possible to keep specification, documentation and example in one place and test the REST API against the specification and use the examples as test cases.		*** [https://github.com/apiaryio/dredd Dredd]+[http://apiblueprint.org/ apiblueprint] (perhaps directly via the webservice at http://apiary.io/) which makes it possible to keep specification, documentation and example in one place and test the REST API against the specification and use the examples as test cases.
	*** [~~https~~://developers.helloreverb.com/swagger/ Swagger]		*** [http://developers.helloreverb.com/swagger/ Swagger]
	*** [https://github.com/mashery/iodocs I/O Docs]		*** [https://github.com/mashery/iodocs I/O Docs]
	** Use static mock json objects under different URLs to provide mock server-side data for testing the webfrontend		** Use static mock json objects under different URLs to provide mock server-side data for testing the webfrontend

Tiziano at 16:24, 11 December 2013

2013-12-11T16:24:06Z

← Older revision		Revision as of 18:24, 11 December 2013
Line 18:		Line 18:
	** Use SeleniumHQ or [http://phantomjs.org/ PhantomJS] for automated testing		** Use SeleniumHQ or [http://phantomjs.org/ PhantomJS] for automated testing
	** Possibly use [http://gruntjs.com/ GruntJS] for an automated workflow		** Possibly use [http://gruntjs.com/ GruntJS] for an automated workflow
	** Use one of the following options for the REST API Testing:		** Use one of the following options for the REST API Testing (& documentation):
	*** [http://frisbyjs.com/ Frisby], partially uses Jasmine and integrates via JUnit XML output with Jenkins		*** [http://frisbyjs.com/ Frisby], partially uses Jasmine and integrates via JUnit XML output with Jenkins
	*** [https://github.com/apiaryio/dredd Dredd]+[http://apiblueprint.org/ apiblueprint] (perhaps directly via the webservice at http://apiary.io/) which makes it possible to keep specification, documentation and example in one place and test the REST API against the specification and use the examples as test cases.		*** [https://github.com/apiaryio/dredd Dredd]+[http://apiblueprint.org/ apiblueprint] (perhaps directly via the webservice at http://apiary.io/) which makes it possible to keep specification, documentation and example in one place and test the REST API against the specification and use the examples as test cases.
			*** [https://developers.helloreverb.com/swagger/ Swagger]
			*** [https://github.com/mashery/iodocs I/O Docs]
	** Use static mock json objects under different URLs to provide mock server-side data for testing the webfrontend		** Use static mock json objects under different URLs to provide mock server-side data for testing the webfrontend

Tiziano at 14:35, 11 December 2013

2013-12-11T14:35:50Z

← Older revision		Revision as of 16:35, 11 December 2013
Line 18:		Line 18:
	** Use SeleniumHQ or [http://phantomjs.org/ PhantomJS] for automated testing		** Use SeleniumHQ or [http://phantomjs.org/ PhantomJS] for automated testing
	** Possibly use [http://gruntjs.com/ GruntJS] for an automated workflow		** Possibly use [http://gruntjs.com/ GruntJS] for an automated workflow
	** ~~Posibly use~~ [http://frisbyjs.com/ Frisby] ~~for~~ REST API ~~Testing~~		** Use one of the following options for the REST API Testing:
			*** [http://frisbyjs.com/ Frisby], partially uses Jasmine and integrates via JUnit XML output with Jenkins
			*** [https://github.com/apiaryio/dredd Dredd]+[http://apiblueprint.org/ apiblueprint] (perhaps directly via the webservice at http://apiary.io/) which makes it possible to keep specification, documentation and example in one place and test the REST API against the specification and use the examples as test cases.
	** Use static mock json objects under different URLs to provide mock server-side data for testing the webfrontend		** Use static mock json objects under different URLs to provide mock server-side data for testing the webfrontend

Tiziano at 14:25, 11 December 2013

2013-12-11T14:25:10Z

← Older revision		Revision as of 16:25, 11 December 2013
Line 18:		Line 18:
	** Use SeleniumHQ or [http://phantomjs.org/ PhantomJS] for automated testing		** Use SeleniumHQ or [http://phantomjs.org/ PhantomJS] for automated testing
	** Possibly use [http://gruntjs.com/ GruntJS] for an automated workflow		** Possibly use [http://gruntjs.com/ GruntJS] for an automated workflow
			** Posibly use [http://frisbyjs.com/ Frisby] for REST API Testing
	** Use static mock json objects under different URLs to provide mock server-side data for testing the webfrontend		** Use static mock json objects under different URLs to provide mock server-side data for testing the webfrontend

Line 23:		Line 24:
	** URLs are specified by stepping stone GmbH		** URLs are specified by stepping stone GmbH
	** URLs have to be bookmarkable		** URLs have to be bookmarkable
	** When using a MVC-Javascript-Framework, the URL will partially be managed by javascript and not directly reach the server, therefore either Yii or the webserver must be able to handle such URLs when a user directly accesses such a page (for example via a bookmark)		** When using a MVC-Javascript-Framework, the URL will partially be managed by javascript and not directly reach the server, therefore either Yii or the webserver must be able to handle such URLs when a user directly accesses such a page ("deep linking", for example via a bookmark). In AngularJS this is supposed to be done by serving the same page as for a an URL higher in the hierarchy and the JavaScript Framework will then do the right thing.

	* Interaction design		* Interaction design
	** When directly accessing a URL and the session is invalid, the user must be forwarded to the requested page after successful authentication (clean referrer handling)		** When directly accessing a URL and the session is invalid, the user must be forwarded to the requested page after successful authentication (clean referrer handling)
	** Back-Button must be working properly, even when using a single-page design (see above)		** Back-Button must be working properly, even when using a single-page design (see above), ensured by using a proper JavaScript framework.
	** Make sure that filters, current page, etc. are preserved when going into detail view of an item and back again		** Make sure that filters, current page, etc. are preserved when going into detail view of an item and back again

Tiziano at 12:56, 11 December 2013

2013-12-11T12:56:47Z

← Older revision		Revision as of 14:56, 11 December 2013
Line 17:		Line 17:
	** Use [http://pivotal.github.io/jasmine/ Jasmine] for JavaScript testing		** Use [http://pivotal.github.io/jasmine/ Jasmine] for JavaScript testing
	** Use SeleniumHQ or [http://phantomjs.org/ PhantomJS] for automated testing		** Use SeleniumHQ or [http://phantomjs.org/ PhantomJS] for automated testing
	** Possibly use [http://gruntjs.com/] for ~~the~~ automated workflow		** Possibly use [http://gruntjs.com/ GruntJS] for an automated workflow
	** Use static mock json objects under different URLs to provide mock server-side data for testing the webfrontend		** Use static mock json objects under different URLs to provide mock server-side data for testing the webfrontend

Tiziano at 12:56, 11 December 2013

2013-12-11T12:56:17Z

← Older revision		Revision as of 14:56, 11 December 2013
Line 2:		Line 2:
	* Use the new [[Application_Programming_Interface_(API)#REST_API \| REST API]].		* Use the new [[Application_Programming_Interface_(API)#REST_API \| REST API]].
	* Use JavaScript framework for the web client.		* Use JavaScript framework for the web client.
	** Use ~~one of the following MVC-Javascript-Framework:~~		** Use [http://angularjs.org/ AngularJS] as base (perhaps starting with [https://github.com/angular/angular-seed Angular Seed]?)
	~~***~~ [http://angularjs.org/ AngularJS]		*** Add [https://github.com/mgonto/restangular Restangular] to make it even easier to connect to the REST-API, see also this [http://stackoverflow.com/questions/16394089/how-to-access-the-services-from-restful-api-in-my-angularjs-page answer on stackoverflow]
	**** Possibly use [https://github.com/mgonto/restangular Restangular] to make it even easier to connect to the REST-API, see also this [http://stackoverflow.com/questions/16394089/how-to-access-the-services-from-restful-api-in-my-angularjs-page answer on stackoverflow]		*** From [http://angular-ui.github.io/bootstrap/ angular-ui] use:
	**** Possibly use [http://angular-ui.github.io/bootstrap/ angular-ui] to integrate with Bootstrap (use bootstrap3 branch)		**** [http://angular-ui.github.io/bootstrap/ UI-Bootstrap] to integrate with Bootstrap (note: you have to use bootstrap3 branch for now)
	*** [http://~~emberjs~~.com/ ~~ember~~]		**** [http://angular-ui.github.io/ui-utils/ UI-Utils] as needed
	*** ([http://~~backbonejs~~.org/ ~~Backbone~~]~~, but requires additional libraries to get to the same functionality as Angular or Ember)~~		**** [https://github.com/angular-ui/ui-router UI-router] as needed
			**** [https://github.com/angular-ui/alias UI-Alias] as needed
			*** Integrate [http://requirejs.org/ RequireJS]
	*** See [http://todomvc.com/ comparison based on a simple webapp]. All suggestions have corresponding Yii extensions.		*** See [http://todomvc.com/ comparison based on a simple webapp]. All suggestions have corresponding Yii extensions.
	* Use HTML5 and not HTML 4.01, not transitional, not XHTML		* Use HTML5 and not HTML 4.01, not transitional, not XHTML
	** ~~Possibly use~~ [http://getbootstrap.com/ bootstrap] (version 3) ~~or [http://html5boilerplate~~.~~com/ HTML5 Boilerplate] (or~~ [http://angular-ui.github.io/bootstrap/ ~~angular~~-ui] ~~when using angular)~~ to get a working pre-defined environment including compat-shims for IE, etc.		** Use [http://getbootstrap.com/ bootstrap] (version 3) resp. [http://angular-ui.github.io/bootstrap/ AngularUI-Bootstrap] to get a working pre-defined environment including compat-shims for IE, etc.

	* Testing		* Testing
	** Use [http://pivotal.github.io/jasmine/ Jasmine] for JavaScript testing		** Use [http://pivotal.github.io/jasmine/ Jasmine] for JavaScript testing
	** Use SeleniumHQ or [http://phantomjs.org/ PhantomJS] for automated testing		** Use SeleniumHQ or [http://phantomjs.org/ PhantomJS] for automated testing
			** Possibly use [http://gruntjs.com/] for the automated workflow
	** Use static mock json objects under different URLs to provide mock server-side data for testing the webfrontend		** Use static mock json objects under different URLs to provide mock server-side data for testing the webfrontend