Work flow of Android Sdk is as follows.
1.)Environmental Setup: it includes installation of android application platform and it’s tools.
During environmental setup process we can also create a virtual device called as (android virtual device), it helps to check the interaction of the application while switching an application from one platform to another one.
2.)Development: during development phase we can make our coding repository with their source code to tune up within the environmental setup to execute it in accordance with user requirement.
3.)Debugging/Testing: as the initial coding phase of the program get ready and accessible in beta domain of the user, in this case tester side (Beta users can apply different testing strategy )
A.)Unit Testing: (uses single component of the source code which is executable)
B.)Integration Testing: (By integrate all the source code )
C.)Negative Testing: (by apply negative outputs to the tuning machine which is executable by the source code check the output result generated by the code)
D.)Load or performance testing: (by applying load to the application with the help automated testing performer tool named as LOAD RUNNER check the consistency of the source code output)
4.)Publishing : In this phase all the units of the source code get compiled or integrated,
And finally check the performance on the dedicated server which is locally hosted in the beta testing environment, and release the beta version for the android application environment.
Before releasing the application the tester (beta user assure to all the bugs which has been raised by them should fix properly). Then only final or alpha version has been released to use for the final end level user to work on the application.