So, at the moment we have basic test that covers kernel+rootfs load and networking(fast ethernet) ability.
Test proposals:
1)
Some test that show that application started (and not failed during startup).
Can be done via any api query like data, version, temperature
2)
Some test that show us that cmos and image capture works (it actually doesn`t covers overall pipeline).
This can be done via /api/debug/umap/vi.json query. There is property IntCnt, that show amount of image frames that captured from cmos. This counter increase during time. Test can query api method several times with sometime delay and compare values:
always 0 cmos not captures
some delta > 0 cmso is capture.
Test can be improved as we can know capturing fps, and we can delay for some reasonable time between api queries, calc average fps and compare with setuped.
3)
Test that capture jpeg, this means that all videopipeline (ok, it`s some basic variant) is working
and we are getting correct jpeg image.
api calls should be determined
Test can be improved, as we can capture sheet with QR code, and we can try recognize that QR code. This requires more facility work, so can be postponed.
Another one test can covers MPP version (api call take it from real SDK api call) with info in family description, that will confirm build consistency.
So, at the moment we have basic test that covers kernel+rootfs load and networking(fast ethernet) ability.
Test proposals:
1) Some test that show that application started (and not failed during startup). Can be done via any api query like data, version, temperature
2) Some test that show us that cmos and image capture works (it actually doesn`t covers overall pipeline). This can be done via /api/debug/umap/vi.json query. There is property IntCnt, that show amount of image frames that captured from cmos. This counter increase during time. Test can query api method several times with sometime delay and compare values:
Test can be improved as we can know capturing fps, and we can delay for some reasonable time between api queries, calc average fps and compare with setuped.
3) Test that capture jpeg, this means that all videopipeline (ok, it`s some basic variant) is working and we are getting correct jpeg image. api calls should be determined
Test can be improved, as we can capture sheet with QR code, and we can try recognize that QR code. This requires more facility work, so can be postponed.