mirror of
				https://github.com/cse110-fa22-group29/cse110-fa22-group29.git
				synced 2025-10-30 19:46:49 +00:00 
			
		
		
		
	update pipeline arch linting and unit testing ADRs
This commit is contained in:
		
							
								
								
									
										19
									
								
								specs/adrs/111222-cicd-multiple-pipelines.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										19
									
								
								specs/adrs/111222-cicd-multiple-pipelines.md
									
									
									
									
									
										Normal file
									
								
							| @@ -0,0 +1,19 @@ | ||||
| # Use multiple CI/CD pipelines in parallel | ||||
|  | ||||
| - Status: accept | ||||
| - Deciders: Arthur Lu, Marc Reta | ||||
| - Date: 11 / 12 / 22 | ||||
|  | ||||
| ## Decision Drivers | ||||
|  | ||||
| - Need to perform many different CI/CD tasks | ||||
| - Need pipeline to be durable against any single failure | ||||
|  | ||||
| ## Considered Options | ||||
|  | ||||
| - Single deep pipeline | ||||
| - Multiple short pipelines in parallel | ||||
|  | ||||
| ## Decision Outcone | ||||
|  | ||||
| Chosen Option: Multiple short pipelines in parallel as any one failure will not prevent code from being developed and deployed.  | ||||
							
								
								
									
										19
									
								
								specs/adrs/111222-jslinting-eslint.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										19
									
								
								specs/adrs/111222-jslinting-eslint.md
									
									
									
									
									
										Normal file
									
								
							| @@ -0,0 +1,19 @@ | ||||
| # Use eslint for JS linting framework | ||||
|  | ||||
| - Status: accept | ||||
| - Deciders: Arthur Lu, Marc Reta | ||||
| - Date: 11 / 12 / 22 | ||||
|  | ||||
| ## Decision Drivers | ||||
|  | ||||
| - Need linting to work with multiple style standards | ||||
| - Need linting to be fast and informative | ||||
|  | ||||
| ## Considered Options | ||||
|  | ||||
| - JSLint | ||||
| - eslint | ||||
|  | ||||
| ## Decision Outcome | ||||
|  | ||||
| Chosen Option: eslint for its low configuration complexity.  | ||||
							
								
								
									
										19
									
								
								specs/adrs/111222-jsunittest-mocha.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										19
									
								
								specs/adrs/111222-jsunittest-mocha.md
									
									
									
									
									
										Normal file
									
								
							| @@ -0,0 +1,19 @@ | ||||
| # Use mocha for JS unit testing framework | ||||
|  | ||||
| - Status: accept | ||||
| - Deciders: Arthur Lu, Marc Reta | ||||
| - Date: 11 / 12 / 22 | ||||
|  | ||||
| ## Decision Drivers | ||||
|  | ||||
| - Need specification on how to write unit testing assertion statements | ||||
| - Need framework to perform unit testing quickly for immediate code feedback | ||||
|  | ||||
| ## Considered Options | ||||
| - JUnit5 | ||||
| - Jest | ||||
| - Mocha | ||||
|  | ||||
| ## Decision Outcome | ||||
|  | ||||
| Chosen Option: Mocha because it was significantly faster to run than Jest (1s vs 30s), and can use a variety of assertion styles unlike JUnit5. | ||||
		Reference in New Issue
	
	Block a user