feat(junit): record app_path in JUnit reports

[alekseiapa]

Description

This PR introduces the feature to record attribute app_path in JUnit reports.

Related

Closes #332

Testing

Added test that ensures that the app_path attribute is correctly recorded for each <testcase> element in the JUnit report.

---

Checklist

Before submitting a Pull Request, please ensure the following:

• 🚨 This PR does not introduce breaking changes.
• All CI checks (GH Actions) pass.
• Documentation is updated as needed.
• Tests are updated or added as necessary.
• Code is well-commented, especially in complex areas.
• Git history is clean — commits are squashed to the minimum necessary.

[alekseiapa]

Hi @hfudev . Please take a look at the changes. Thanks!

[horw]

Shall we also add a test for test_idf.py to ensure it works with apps?

[hfudev]

overall LGTM. a few comments posted

[hfudev]

question, why can't we use the attrib['name'] here?

[alekseiapa]

The issue is that in some cases, the pytest test case name is being replaced by the C test case name, resulting in the name being absent in the mapping.

[hfudev]

I see. so I have a different implementation of the whole task.

single-dut test cases

instead of your current modify main junit report way, we could record the app_path directly. for example,

in

pytest-embedded/pytest-embedded/pytest_embedded/dut.py

Line 190 in 3f00082

self.testsuite.add_unity_test_cases(log)

it could be self.testsuite.add_unity_test_cases(log, test_case_name=self.test_case_name , which writes the test_case_name to pytest_case_name

multi-dut test cases

we could modify this function instead

pytest-embedded/pytest-embedded-idf/pytest_embedded_idf/unity_tester.py

Line 654 in e3856b5

def process_raw_report_data(self, raw_data_to_report) -> t.Dict:

to insert the pytest_case_name

---

by these approaches, the data we recorded in the objects is correct. we don't have to generate the wrong one first, then write a function to replace the wrong one into correct ones.

[alekseiapa]

Unfortunately, this suggestion isn't viable. For example, self.testsuite.add_unity_test_cases is executed only within the expect_unity_test_output context. However, there are numerous scenarios where users call expect_exact. Additionally, I tested it on the provided tests in this PR, and in both cases, the proposed solution either fails to work or requires significantly more changes compared to the current implementation.

[hfudev]

I made this work in #338, please take a look. I'll close this PR.