Running in parallel

[Chemaclass]

📚 Description

Closes: #354

🔖 Changes

• Add parallel running: -p|--parallel
• Add possibility of disabling parallel execution with --no-parallel

✅ To-do list

• I updated the CHANGELOG.md to reflect the new feature or fix
• I updated the documentation to reflect the changes

🖼️ Screenshots

Running the entire test suite sync (~43s)

Running the entire test suite in parallel (~15s) - 65.12% improment! 🚀

Running parallel tests (detailed)

Documentation

[CosmeValera]

Good job as always !!!

[khru]

I would just say that for me parallel testing should always be the default way to run, as it is not just for performance, but also to know that your tests do not depend on each other,

I would rather suggest that it be always active by default in subsequent versions and that it can be disabled.

That's my opinion, I think that the value that active brings is always greater, and that only in case you need to disable it because your code needs it, you do it.

This opens up other issues such as being able to prevent a test file from being launched in parallel, this is common in other testing frameworks.

[khru]

The tests are not good in alpine

[Chemaclass]

I would rather not keep the parallel testing as default behavior but as it was until now.
This is the default behavior on PHPUnit, Pest, JUnit, among others. However I found that Jest run them in parallel "when it make sense" based on some heuristic -size of tests, number of tests, etc... but I find this too complicated to get into this right now.

Aiming for simplicity, I am in favor of:
If you want parallel tests you can enable with -p|--parallel or in your .env BASHUNIT_PARALLEL_RUN=true

---

PS: Yes, I saw something is not good in alpine. I will check it... 🏗️

[Chemaclass]

📚 Description

Closes: #354

🔖 Changes

• Add parallel running: -p|--parallel
• Add possibility of disabling parallel execution with --no-parallel

✅ To-do list

• I updated the CHANGELOG.md to reflect the new feature or fix
• I updated the documentation to reflect the changes

🖼️ Screenshots

Running the entire test suite sync (~43s)

Running the entire test suite in parallel (~15s) - 65.12% improment! 🚀

Running parallel tests (detailed)

Documentation

[CosmeValera]

Good job as always !!!

[khru]

I would just say that for me parallel testing should always be the default way to run, as it is not just for performance, but also to know that your tests do not depend on each other,

I would rather suggest that it be always active by default in subsequent versions and that it can be disabled.

That's my opinion, I think that the value that active brings is always greater, and that only in case you need to disable it because your code needs it, you do it.

This opens up other issues such as being able to prevent a test file from being launched in parallel, this is common in other testing frameworks.

[khru]

The tests are not good in alpine

[Chemaclass]

I would rather not keep the parallel testing as default behavior but as it was until now.
This is the default behavior on PHPUnit, Pest, JUnit, among others. However I found that Jest run them in parallel "when it make sense" based on some heuristic -size of tests, number of tests, etc... but I find this too complicated to get into this right now.

Aiming for simplicity, I am in favor of:
If you want parallel tests you can enable with -p|--parallel or in your .env BASHUNIT_PARALLEL_RUN=true

---

PS: Yes, I saw something is not good in alpine. I will check it... 🏗️

[Chemaclass]

📚 Description

Closes: #354

🔖 Changes

• Add parallel running: -p|--parallel
• Add possibility of disabling parallel execution with --no-parallel

✅ To-do list

• I updated the CHANGELOG.md to reflect the new feature or fix
• I updated the documentation to reflect the changes

🖼️ Screenshots

Running the entire test suite sync (~43s)

Running the entire test suite in parallel (~15s) - 65.12% improment! 🚀

Running parallel tests (detailed)

Documentation

[CosmeValera]

Good job as always !!!

[khru]

I would just say that for me parallel testing should always be the default way to run, as it is not just for performance, but also to know that your tests do not depend on each other,

I would rather suggest that it be always active by default in subsequent versions and that it can be disabled.

That's my opinion, I think that the value that active brings is always greater, and that only in case you need to disable it because your code needs it, you do it.

This opens up other issues such as being able to prevent a test file from being launched in parallel, this is common in other testing frameworks.

[khru]

The tests are not good in alpine

[Chemaclass]

I would rather not keep the parallel testing as default behavior but as it was until now.
This is the default behavior on PHPUnit, Pest, JUnit, among others. However I found that Jest run them in parallel "when it make sense" based on some heuristic -size of tests, number of tests, etc... but I find this too complicated to get into this right now.

Aiming for simplicity, I am in favor of:
If you want parallel tests you can enable with -p|--parallel or in your .env BASHUNIT_PARALLEL_RUN=true

---

PS: Yes, I saw something is not good in alpine. I will check it... 🏗️

[Chemaclass]

📚 Description

Closes: #354

🔖 Changes

• Add parallel running: -p|--parallel
• Add possibility of disabling parallel execution with --no-parallel

✅ To-do list

• I updated the CHANGELOG.md to reflect the new feature or fix
• I updated the documentation to reflect the changes

🖼️ Screenshots

Running the entire test suite sync (~43s)

Running the entire test suite in parallel (~15s) - 65.12% improment! 🚀

Running parallel tests (detailed)

Documentation

[CosmeValera]

Good job as always !!!

[khru]

I would just say that for me parallel testing should always be the default way to run, as it is not just for performance, but also to know that your tests do not depend on each other,

I would rather suggest that it be always active by default in subsequent versions and that it can be disabled.

That's my opinion, I think that the value that active brings is always greater, and that only in case you need to disable it because your code needs it, you do it.

This opens up other issues such as being able to prevent a test file from being launched in parallel, this is common in other testing frameworks.

[khru]

The tests are not good in alpine

[Chemaclass]

I would rather not keep the parallel testing as default behavior but as it was until now.
This is the default behavior on PHPUnit, Pest, JUnit, among others. However I found that Jest run them in parallel "when it make sense" based on some heuristic -size of tests, number of tests, etc... but I find this too complicated to get into this right now.

Aiming for simplicity, I am in favor of:
If you want parallel tests you can enable with -p|--parallel or in your .env BASHUNIT_PARALLEL_RUN=true

---

PS: Yes, I saw something is not good in alpine. I will check it... 🏗️

[Chemaclass]

📚 Description

Closes: #354

🔖 Changes

• Add parallel running: -p|--parallel
• Add possibility of disabling parallel execution with --no-parallel

✅ To-do list

• I updated the CHANGELOG.md to reflect the new feature or fix
• I updated the documentation to reflect the changes

🖼️ Screenshots

Running the entire test suite sync (~43s)

Running the entire test suite in parallel (~15s) - 65.12% improment! 🚀

Running parallel tests (detailed)

Documentation

[CosmeValera]

Good job as always !!!

[khru]

I would just say that for me parallel testing should always be the default way to run, as it is not just for performance, but also to know that your tests do not depend on each other,

I would rather suggest that it be always active by default in subsequent versions and that it can be disabled.

That's my opinion, I think that the value that active brings is always greater, and that only in case you need to disable it because your code needs it, you do it.

This opens up other issues such as being able to prevent a test file from being launched in parallel, this is common in other testing frameworks.

[khru]

The tests are not good in alpine

[Chemaclass]

I would rather not keep the parallel testing as default behavior but as it was until now.
This is the default behavior on PHPUnit, Pest, JUnit, among others. However I found that Jest run them in parallel "when it make sense" based on some heuristic -size of tests, number of tests, etc... but I find this too complicated to get into this right now.

Aiming for simplicity, I am in favor of:
If you want parallel tests you can enable with -p|--parallel or in your .env BASHUNIT_PARALLEL_RUN=true

---

PS: Yes, I saw something is not good in alpine. I will check it... 🏗️

[Chemaclass]

📚 Description

Closes: #354

🔖 Changes

• Add parallel running: -p|--parallel
• Add possibility of disabling parallel execution with --no-parallel

✅ To-do list

• I updated the CHANGELOG.md to reflect the new feature or fix
• I updated the documentation to reflect the changes

🖼️ Screenshots

Running the entire test suite sync (~43s)

Running the entire test suite in parallel (~15s) - 65.12% improment! 🚀

Running parallel tests (detailed)

Documentation

[CosmeValera]

Good job as always !!!

[khru]

I would just say that for me parallel testing should always be the default way to run, as it is not just for performance, but also to know that your tests do not depend on each other,

I would rather suggest that it be always active by default in subsequent versions and that it can be disabled.

That's my opinion, I think that the value that active brings is always greater, and that only in case you need to disable it because your code needs it, you do it.

This opens up other issues such as being able to prevent a test file from being launched in parallel, this is common in other testing frameworks.

[khru]

The tests are not good in alpine

[Chemaclass]

I would rather not keep the parallel testing as default behavior but as it was until now.
This is the default behavior on PHPUnit, Pest, JUnit, among others. However I found that Jest run them in parallel "when it make sense" based on some heuristic -size of tests, number of tests, etc... but I find this too complicated to get into this right now.

Aiming for simplicity, I am in favor of:
If you want parallel tests you can enable with -p|--parallel or in your .env BASHUNIT_PARALLEL_RUN=true

---

PS: Yes, I saw something is not good in alpine. I will check it... 🏗️

[Chemaclass]

📚 Description

Closes: #354

🔖 Changes

• Add parallel running: -p|--parallel
• Add possibility of disabling parallel execution with --no-parallel

✅ To-do list

• I updated the CHANGELOG.md to reflect the new feature or fix
• I updated the documentation to reflect the changes

🖼️ Screenshots

Running the entire test suite sync (~43s)

Running the entire test suite in parallel (~15s) - 65.12% improment! 🚀

Running parallel tests (detailed)

Documentation

[CosmeValera]

Good job as always !!!

[khru]

I would just say that for me parallel testing should always be the default way to run, as it is not just for performance, but also to know that your tests do not depend on each other,

I would rather suggest that it be always active by default in subsequent versions and that it can be disabled.

That's my opinion, I think that the value that active brings is always greater, and that only in case you need to disable it because your code needs it, you do it.

This opens up other issues such as being able to prevent a test file from being launched in parallel, this is common in other testing frameworks.

[khru]

The tests are not good in alpine

[Chemaclass]

I would rather not keep the parallel testing as default behavior but as it was until now.
This is the default behavior on PHPUnit, Pest, JUnit, among others. However I found that Jest run them in parallel "when it make sense" based on some heuristic -size of tests, number of tests, etc... but I find this too complicated to get into this right now.

Aiming for simplicity, I am in favor of:
If you want parallel tests you can enable with -p|--parallel or in your .env BASHUNIT_PARALLEL_RUN=true

---

PS: Yes, I saw something is not good in alpine. I will check it... 🏗️

[Chemaclass]

📚 Description

Closes: #354

🔖 Changes

• Add parallel running: -p|--parallel
• Add possibility of disabling parallel execution with --no-parallel

✅ To-do list

• I updated the CHANGELOG.md to reflect the new feature or fix
• I updated the documentation to reflect the changes

🖼️ Screenshots

Running the entire test suite sync (~43s)

Running the entire test suite in parallel (~15s) - 65.12% improment! 🚀

Running parallel tests (detailed)

Documentation

[CosmeValera]

Good job as always !!!

[khru]

I would just say that for me parallel testing should always be the default way to run, as it is not just for performance, but also to know that your tests do not depend on each other,

I would rather suggest that it be always active by default in subsequent versions and that it can be disabled.

That's my opinion, I think that the value that active brings is always greater, and that only in case you need to disable it because your code needs it, you do it.

This opens up other issues such as being able to prevent a test file from being launched in parallel, this is common in other testing frameworks.

[khru]

The tests are not good in alpine

[Chemaclass]

I would rather not keep the parallel testing as default behavior but as it was until now.
This is the default behavior on PHPUnit, Pest, JUnit, among others. However I found that Jest run them in parallel "when it make sense" based on some heuristic -size of tests, number of tests, etc... but I find this too complicated to get into this right now.

Aiming for simplicity, I am in favor of:
If you want parallel tests you can enable with -p|--parallel or in your .env BASHUNIT_PARALLEL_RUN=true

---

PS: Yes, I saw something is not good in alpine. I will check it... 🏗️