magiclantern_simplified icon indicating copy to clipboard operation
magiclantern_simplified copied to clipboard

Define required testing for new cams

Open reticulatedpines opened this issue 2 months ago • 0 comments

Similar to issue #152 - what testing do we require for newly supported cams before we can release a build for them?

Currently it is this list: 200D 5D4 6D2 750D 77D 7D2 80D

There is no qemu automation for these cams. Selftest module is not compatible with these cams and is dangerous to run. It tries to test things that rely on assumptions about D45 behaviour, e.g. attempting to over allocate from SRM system (safe error on D45, breaks SRM subsystem on D678), or use of null pointers.

Possibly, manual testing of the limited feature set is adequate for an initial release. I did make a modernised framework for qemu testing, and it's nicer in many ways than the old system... but it also is far from finished. Currently it does very little, though it would allow creating new tests.

This ticket is for discussion, leading to a well described testing plan we can follow for all new cams.

reticulatedpines avatar Dec 14 '24 13:12 reticulatedpines