To meaningfully work on this ticket likely means having a most of the test suite for demand done, so that this can be integrated as the signal. The technique for testing reports we've used before can be seen here. I think it makes sense to wrap the report generation in function as a pytest fixture (which I assume is not cached, but I'd need to check) and make the individual tests/ demand checkpoints cleaner. This will likely be satisfied by checking the demand after each transaction, coordinated with pytest-order.
I think a secondary feature of this report should be the ability to sort the by operation and/or workstation viewing the demand date. This would allow the user to decide if it makes sense to do the same operation at the same workstation or if it should be switched.
To meaningfully work on this ticket likely means having a most of the test suite for demand done, so that this can be integrated as the signal. The technique for testing reports we've used before can be seen here. I think it makes sense to wrap the report generation in function as a pytest fixture (which I assume is not cached, but I'd need to check) and make the individual tests/ demand checkpoints cleaner. This will likely be satisfied by checking the demand after each transaction, coordinated with pytest-order.
I think a secondary feature of this report should be the ability to sort the by operation and/or workstation viewing the demand date. This would allow the user to decide if it makes sense to do the same operation at the same workstation or if it should be switched.