Added requirement for Cobertura XML report. Closes #22.

[EmbeddedDevops1]

User description

Added requirement for Cobertura XML report. Closes #22.

---

PR Type

documentation

---

Description

• Added requirement for generating a Cobertura XML code coverage report in the README.
• Provided an example using pytest-cov to generate the Cobertura XML report.
• Mentioned that more coverage types are being worked on and encouraged contributions.

---

Changes walkthrough 📝

	Relevant files
Documentation	README.md Added requirement and instructions for Cobertura XML report README.md Added requirement for Cobertura XML code coverage report. Provided example for generating Cobertura XML report using pytest-cov. Mentioned ongoing work for supporting more coverage types. +3/-0

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[qodo-merge-pro]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	1, because the changes are limited to documentation updates in the README.md file. The modifications are straightforward and do not involve complex code changes.
🧪 Relevant tests	No
⚡ Possible issues	No
🔒 Security concerns	No

[qodo-merge-pro]

PR Code Suggestions ✨

Category	Suggestion	Score
Clarity	Clarify that the Cobertura XML report is a required component for the tool To improve clarity, specify that the Cobertura XML report is required for the tool to function correctly. This will help users understand the necessity of this requirement. README.md [54] -- Code Coverage tool: You'll need to have your tests also generate a Cobertura XML code coverage report. +- Code Coverage tool: A Cobertura XML code coverage report is required for the tool to function correctly. Suggestion importance[1-10]: 7 Why: The suggestion correctly identifies an improvement in clarity by specifying the necessity of the Cobertura XML report, which is crucial for users to understand its importance.	7
Readability	Split a long sentence into two shorter sentences for better readability To enhance readability, break the second sentence into two separate sentences. This will make the instructions easier to follow. README.md [55] -- For example, in Python one could use `pytest-cov` and add the `--cov-report=xml` option when running Pytest +- For example, in Python one could use `pytest-cov`. Add the `--cov-report=xml` option when running Pytest. Suggestion importance[1-10]: 6 Why: Splitting a long sentence into two can indeed enhance readability, making the instructions clearer and easier to follow.	6
Consistency	Add a period at the end of the first bullet point for consistency To ensure consistency, use the same punctuation style for all bullet points. Add a period at the end of the first bullet point to match the second and third bullet points. README.md [54] Suggestion importance[1-10]: 5 Why: The suggestion to add a period for consistency is valid, though it is a minor stylistic change and does not impact the understanding significantly.	5
Flow	Move the note about contributing to the end of the section for better information flow To improve the flow of information, move the note about contributing to the end of the section. This keeps the instructions focused and places additional information at the end. README.md [56] -- Note: We are actively working on adding more coverage types but please feel free to open a PR and contribute to `cover_agent/CoverageProcessor.py` +Note: We are actively working on adding more coverage types. Please feel free to open a PR and contribute to `cover_agent/CoverageProcessor.py`. Suggestion importance[1-10]: 4 Why: While the suggestion might improve the flow of information, it does not reflect a change in the actual code diff provided. The suggestion to move the note is not derived from the PR code diff, hence the lower score.	4