fac10 / research Goto Github PK

Over time, the research topics in master-reference may change.

To have a record of what was asked of this cohort, it would be useful to link to the instructions, as they were at that point in FAC history

There is a small change in readme topics for week 2: I removed manual testing vs automation testing.
As automation testing means using Continuous integration, which are not covered in week 2, there is no point to introduce it.

Please add a link in the readme to your week-7/validation.md

Would this team please:

• add the relevant file to the week 6 folder and/or move the relevant repo into the FAC10 organisation
• update the README.md with a link

Would this team please:

• add the relevant file to the week 2 folder and/or move the relevant repo into the FAC10 organisation
• update the README.md with a link

Would this team please:

• add the relevant file to the week 7 folder and/or move the relevant repo into the FAC10 organisation
  FAC10/Postgresql-Testing#2

• update the README.md with a link

Thanks for pointing this out @oliverjam !

• For the Git & Github research topic, this format does not make sense with this brief

(Whereas this does make sense for the accessibility and css topics)

• The name should also be "git & github" as per the brief, rather than just "git"

Please add relevant readme

Would this team please:

• add the relevant file to the week 6 folder and/or move the relevant repo into the FAC10 organisation
• update the README.md with a link

Would this team please:

• add the relevant file to the week 5 folder and/or move the relevant repo into the FAC10 organisation
• update the README.md with a link

The readme link currently goes to an old version of this research repo: https://github.com/FAC10/research/tree/65566b076fa11c4f9228712b4f505c0b97711655

Would this team please update the README.md with a link to the file inside the week-4 folder

I should have changed the CONTRIBUTING.md file when I submitted PR #6 for issue #3
Oops 🙀