tests: add test for the aconno board acd52832

[ghost]

This PR includes the test for the aconno board ACD52832.

Following features are integrated:

• Toggle of LED LD2 (over MCP23017)
• Joystick control S4 (over MCP23017)

And following PRs are required:

• boards: add acd52832/nrf52832 #7501
• drivers: add i2c driver for nrf52 #7557
• drivers: add driver mcp23017 #7652

[smlng]

sorry but IMHO board specific tests are a bit against the general concept here. You should rather add a test for your mcp27017 driver instead - looks like you could start by renaming this one and maybe adapt 1 or 2 things ....

[ghost]

The idea was to expand this test later with features like the electronic paper display.
@smlng What do you think about?

[smlng]

still not convinced - as said: this would be against the current concept of having board independent tests. The mcp27013 or the e-paper display could be attached to any board (in theory). So there should rather be tests for these devices, first.

Nevertheless, I do see the merits of having board specific tests that check all the peripheral devices attached to a board at once. But that would be an extension of the current test framework, and definitely needs to be discussed in a broader scope -> maybe write an email to devel/maintainer mailing list.

[smlng]

I guess at least @kaspar030 and @miri64 might have an opinion on that, too.

We could also think about having a separate repo for such tests?

[kaspar030]

this would be against the current concept of having board independent tests. The mcp27013 or the e-paper display could be attached to any board (in theory). So there should rather be tests for these devices, first.

Agreed. If the tests are not dependent on each other (e.g., a motor can only be controlled through a joystick, thus a test application for it would need to include the joystick "test"), they should be in separate, board-independent test applications.

[PeterKietzmann]

As agreed offline we close this PR now.