Hi Aamod,
The definition of Check-in and Check-out is different in HANA workspace based development.
If you Check-out an object( models or .hdb objects), then it doesn't locks it from being changed by any other user. Also, there is no option to Check-IN an object.
So if two users are working on same file, then whoever activates first will get his changes saved in the repository. The second developer will receive an error when he activate his version of same file - Activation Failed...another higher version caused an activation. To resolve this, difference between object in repository and second developer's local workspace have to be corrected manually by going to synchronize view.
Export of Delivery Unit will bring in all the objects from DEV to Test environment. So, to have a control on what objects should get migrated, you can go for Change Manager.
Open a separate thread and we can discuss your concerns about migration.
Message was edited by: Tarun Gupta