QA/Execution/Web Testing/Docs/Automation/StyleGuide: Difference between revisions

QA/Execution/Web Testing/Docs/Automation/StyleGuide (view source)

11 bytes removed , 26 September 2013

Confirmed users

425

edits

Revision as of 16:26, 20 April 2012 (view source) Davehunt (talk \| contribs) (→‎Page Objects) ← Older edit		Revision as of 13:46, 26 September 2013 (view source) Bobsilverberg (talk \| contribs) (→‎Using new and old standards together) Newer edit →
Line 181:		Line 181:
	As we (and Selenium and automation) develop more knowledge some projects might fall behind the standards in this style guide. It can be tempting to want to fix all of the outdated style but in order to keep patches/pulls small (see above!) we are happy to have new and old standards of code sit side by side. As we regularly review and update tests the project will be brought completely up to our current standards.		As we (and Selenium and automation) develop more knowledge some projects might fall behind the standards in this style guide. It can be tempting to want to fix all of the outdated style but in order to keep patches/pulls small (see above!) we are happy to have new and old standards of code sit side by side. As we regularly review and update tests the project will be brought completely up to our current standards.

	Or if you prefer, log a ~~Pivotal job or an~~ issue to have a section of code addressed separately to the job you are doing.		Or if you prefer, log a Github issue to have a section of code addressed separately to the job you are doing.