#### Functional
###### Has the requirement for the allowed packages been respected? (Reminder for this project: (only [standard packages](https://golang.org/pkg/))
###### Does the project contain HTML files?
##### Try inputting with the standard template/banner the following example:
In the first line `{123}`
In the second line `<Hello> (World)!`
```
Refactor & Beautify & destruction commit
return early, remove else branches, reorder conditions and top-level functions, remove empty lines, remove unnecessary append(), fix typos, stop using testing package, remove dead code, fix mistakes in subjects, tests and solutions, remove disclaimers, reformat comments, simplify solutions, tests, add more instructions to subjects, remove obsolete files, etc.
Some of the reasons behind those modifications will be added to good-practices.en.md
Some of the exercises are now broken, they will have to be fixed, most of them have a "TODO:" comment.
5 years ago
__ __
/ / _ ____ _____ \ \
| | / | |___ \ |___ / | |
/ / | | __ ) | |_ \ \ \
\ \ | | / __ / ___) | / /
| | |_| |_____| |____/ | |
\_\ /_/
__ _ _ _ _ __ __ __ __ _ _ __ _
/ / | | | | | | | | \ \ / / \ \ / / | | | | \ \ | |
/ / | |__| | ___ | | | | ___ \ \ | | \ \ /\ / / ___ _ __ | | __ | | | | | |
< < | __ | / _ \ | | | | / _ \ > > | | \ \/ \/ / / _ \ | '__| | | / _` | | | | |
\ \ | | | | | __ / | | | | | (_) | / / | | \ /\ / | (_) | | | | | | (_| | | | |_|
\_\ |_| |_| \___| |_| |_| \___/ /_/ | | \/ \/ \___/ |_| |_| \__,_| | | (_)
\_\ /_/
```
###### Does it display the right result as above?
##### Try to input `123??` using the template/banner standard.
```
Refactor & Beautify & destruction commit
return early, remove else branches, reorder conditions and top-level functions, remove empty lines, remove unnecessary append(), fix typos, stop using testing package, remove dead code, fix mistakes in subjects, tests and solutions, remove disclaimers, reformat comments, simplify solutions, tests, add more instructions to subjects, remove obsolete files, etc.
Some of the reasons behind those modifications will be added to good-practices.en.md
Some of the exercises are now broken, they will have to be fixed, most of them have a "TODO:" comment.
5 years ago
___ ___
_ ____ _____ |__ \ |__ \
/ | |___ \ |___ / ) | ) |
| | __ ) | |_ \ / / / /
| | / __ / ___) | |_| |_|
|_| |_____| |____/ (_) (_)
```
###### Does it display the right result as above?
##### Try to input `$% "=` using the template/banner shadow.
```
Refactor & Beautify & destruction commit
return early, remove else branches, reorder conditions and top-level functions, remove empty lines, remove unnecessary append(), fix typos, stop using testing package, remove dead code, fix mistakes in subjects, tests and solutions, remove disclaimers, reformat comments, simplify solutions, tests, add more instructions to subjects, remove obsolete files, etc.
Some of the reasons behind those modifications will be added to good-practices.en.md
Some of the exercises are now broken, they will have to be fixed, most of them have a "TODO:" comment.
5 years ago
_| _ |
_| _ |_| _| _ | _|
_|_|_| _|_ | _| _ |_|_|_|_|
_|_| _|
_|_ | _| _ |_| _|_ |_|_|_|
_|_|_| _| _ |_|
_|
```
###### Does it display the right result as above?
##### Try to input `123 T/fs#R` using the template/banner thinkertoy.
```
Refactor & Beautify & destruction commit
return early, remove else branches, reorder conditions and top-level functions, remove empty lines, remove unnecessary append(), fix typos, stop using testing package, remove dead code, fix mistakes in subjects, tests and solutions, remove disclaimers, reformat comments, simplify solutions, tests, add more instructions to subjects, remove obsolete files, etc.
Some of the reasons behind those modifications will be added to good-practices.en.md
Some of the exercises are now broken, they will have to be fixed, most of them have a "TODO:" comment.
5 years ago
0 -- o-o o-O-o o o-o | | o--o
/| o o | | / | -O-O- | |
o | / oo | o -O- o-o | | O-Oo
| / | | / | \ -O-O- | \
o-o-o o--o o-o o o o o-o | | o o
```
###### Does it display the right result as above?
###### Does it display an understandable graphical representation of the result?
##### Try to navigate between all the available pages in the website.
###### Are all the pages working? Does the project implement [404 status](https://www.restapitutorial.com/httpstatuscodes.html)?
###### Does the project handle [HTTP status 400 - Bad Request](https://kinsta.com/knowledgebase/400-bad-request/#causes)?
###### Does the project handle [HTTP status 500 - Internal Server Errors](https://www.restapitutorial.com/httpstatuscodes.html)?
##### Try making a request to the server (clicking a button to generate the ascii-art representation on the website)
###### Is the communication between [server and client](https://www.geeksforgeeks.org/client-server-model/) well established?
###### Does the server uses the right [HTTP method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods)?
###### Did the site work without crashing at any time?
###### Is the server written in Go?
###### As an auditor, is this project up to every standard? If not, why are you failing the project?(Empty Work, Incomplete Work, Invalid compilation, Cheating, Crashing, Leaks)
#### General
###### +Does the server present all the needed [handlers and patterns](https://golang.org/pkg/net/http/#HandleFunc) for the http requests?
#### Basic
###### +Does the server run quickly and effectively? (Favoring recursive, no unnecessary data requests, etc)
###### +Does the code obey the [good practices](../../good-practices/README.md)?
###### +Is there a test file for this code?
###### +Are the tests checking each possible case?
###### +Are the instructions in the website clear?
###### +Does the project run using an API?
#### Social
###### +Did you learn anything from this project?
###### +Can it be open-sourced / be used for other sources?
###### +Would you recommend/nominate this program as an example for the rest of the school?
