sorry I have none that are suited for testing. We have to create a small installation of every release of OpenMeetings starting by v1.4 and do an export, otherwise you can't really compare what data is existing and what you should expected after the import. It is important that we do - at least create 2 users, - upload a profile image for at least one of the users, - create and assign one user to at least one other to be created organization, - create 1 regular recording with audio/video turned on, - create 1 interview recording, - upload a PPT in a conference room, - create a folder in the file explorer, - upload at least one file to the private section of a users file explorer, - create 1 more conference room in the admin UI, - create 1 calendar event with an attached conference room and at least 1 internal invitee and at least 1 external invitee, - send one private message from on user to the other, - add one contact to the list of contacts in the user list (eventually with right to share calendar), - add or modify one configuration
And after the import we have to control if all this data is just the way it was in the old exported system. Only then we can really judge if the import is ok. My idea was to create a JUnit test that does the import and afterwards JUnit does a couple of checks on the tables and on the file-system where the imported data and files should be. That way we do not need to control all the data or "import success" manually after each import test. Sebastian 2013/1/30 Maxim Solodovnik <[email protected]> > Hello Sebastian, > > Can you provide me with backup files from old versions of OM? > I promise to clean up all sensitive information before using it in the > automated backup test :)) > > > -- > WBR > Maxim aka solomax > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
