Sure, you can find it in this link

http://archive.ics.uci.edu/ml/datasets.html?format=&task=clu&att=&area=&numAtt=&numIns=&type=&sort=nameUp&view=table

Mohammad Bazmara .....thanks for uci DATA SET

@ Mamta

They reside on different concepts all together. Mobile applications are fundamentally different (also depending on their platforms, as not all apps are the same) from desktop applications because of the layers they stack up on. The typical desktop app (these days they may be RTE based) rely upon core libraries and might involve a lot more client-side processing (desktop apps may not even be client-server based). 

So how would you address the two problems? One side ('proper' mobile app), necessitates server side service support, but the other an application test case simply may or may not  need server alignment (assuming standardization is your goal) - furthermore, for test cases, do you expect them to be complex? Obviously, the permutations in such cases for the mobile platform are expected to be a lot more less than in comparison to a desktop app, probably determined by depth of functionalities.

Why do you test an application? Ask this question first - then, enumerate these functionalities and then determine the type of testing (white box? random?). Obviously justify this too. More importantly, know the limitations of your application and then determine the testing model. Do note, each test case is expected to be different.

And you should avoid random testing if you're testing a mobile platform due to its scale. Think of it as covering ground - if the ground your treading is 'smaller' you should be able to walk across it all to ascertain consistency - but if it's too big, you will have to take larger steps. Same concepts applied here.

Mobile applications are expected to be light weight - but desktop apps may get a little heavy - the trend these days is to shed unnecessary weight off these apps - make sure that processing is lighter and is more server side etc. Even when programming I tend to look for ways to be lighter and leaner with my desktop apps, pushing all the processing needs to a server.

So with this, obviously, testing will evolve - but note that the challenge is to standardize. So, more effort is needed in identifying your primary indicators/variables etc.

Hope this helps.