You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+41-23Lines changed: 41 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,48 +1,67 @@
1
1
# Contribution
2
2
3
-
## Install
3
+
## Requirements
4
4
5
-
This project uses a Makefile to run scripts. You can run `make help` to get the list of commands.
5
+
1. Maven 3.9.6+
6
+
2. Java JDK 11
6
7
7
-
## How to contribute
8
+
## Install and Testing Locally
8
9
9
-
### 1. Clone the repository
10
+
`mvn clean install`
10
11
11
-
Now clone the repository from GitHub to your computer.
12
+
The project uses JUnit with Mutation tests and IT tests.
12
13
13
-
### 2. Create a branch
14
+
1.[Jupiter aka Junit5](https://junit.org/junit5/)
15
+
2.[PIT](https://pitest.org/)
16
+
3.[Maven IT extenstion](https://github.com/khmarbaise/maven-it-extension)
14
17
15
-
This repository not supports forking. So, create a branch named accord what you want to contribute to.
18
+
Before adding new code, make sure to add test cases for it so that the maintainers can provide guidance and simulate the same scenarios.
16
19
17
-
```
18
-
git checkout -b <add-your-new-branch-name>
19
-
```
20
+
### Unit Tests
20
21
21
-
For example:
22
+
1. They're just conventional JUnit tests.
23
+
2. Avoid excessive mocks.
24
+
3. Try to use the AAA structure, stands for: Arrange, Act, Assert
25
+
4. Ensure all the mutations were killed and covered.
22
26
23
-
```
24
-
git checkout -b add-alonzo-church
25
-
```
27
+
### Integration Tests
26
28
27
-
### 3. Commit your changes
29
+
1. Make sure to add your project scenario to the `resources-it` folder.
30
+
2. Include your IT scenario in the class `TemplifyIT`. (This class is responsible for executing the Maven plugin build for the project scenarios)
31
+
3. Ensure the tests are marked as `@MavenTest` and have meaningful asserts.
32
+
33
+
If you face any issue about the
34
+
35
+
## How to contribute
28
36
29
-
Now open `Contributors.md` file in a text editor, add your name to it. Don't add it at the beginning or end of the file. Put it anywhere in between. Now, save the file.
If you go to the project directory and execute the command `git status`, you'll see there are changes. Add those changes to the branch you just created using the `git add` command:
41
+
### 2. Create a branch to add your changes
33
42
34
43
```
35
-
git add Contributors.md
44
+
git switch -C <add-your-new-branch-name>
36
45
```
37
46
38
-
Now commit those changes using the `git commit` command:
47
+
For example:
39
48
40
49
```
41
-
git commit -m "Add <your-name> to Contributors list"
50
+
git switch -C update-readme
42
51
```
43
52
44
-
Replacing `<your-name>` with your name.
53
+
### 3. Commit your changes
45
54
55
+
This repository uses the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) standard.
56
+
57
+
For example:
58
+
-
59
+
```
60
+
git commit -m "feat: add new feature"
61
+
git commit -m "docs: correct spelling of CHANGELOG"
62
+
git commit -m "feat(api)!: send an email to the customer when a product is shipped"
63
+
64
+
```
46
65
47
66
### 4. Push to the original branch
48
67
@@ -67,12 +86,11 @@ Soon I'll be merging all your changes into the main branch of this project. You
67
86
68
87
Congrats!
69
88
70
-
You just completed the standard `clone -> branch -> commits -> PR_` workflow that you'll often encounter as a contributor!
89
+
You just completed the standard `fork/clone -> branch -> commits -> PR_` workflow that you'll often encounter as a contributor!
0 commit comments