Unit
testing for Android is quite
simple as the API
uses the JUnit testing
framework. The JUnit
framework enforces the hierarchical organization of the various
test units, which is a big plus. Moreover, the pattern of JUnit guarantees the independence of the test units and minimizes
interference. This is done by
first creating and
then destroying the environment
newly created test before and after each test
method is executed. Android
JUnit even takes a
step further by allowing the
device to test the code. Here, test
libraries are incorporated as part of the standard libraries of Android.
However, there is a problem with the Android device in the tests compared to Windows Mobile is the readability of the results. Evidence of Android devices do not have a user interface that can display test results. To see the results of the test, a controller that handles the callbacks Android test runner has to be implemented.
Windows Mobile, on the other hand has a high degree of legibility and visibility, while the Android platform is a bit difficult to use when it comes to efficiency. The problem with Android is the lack of information, which is issued automatically through visual tools in the integrated development environment in Windows Mobile.
Windows Mobile implements a version of the xUnit framework. The code for the test class is held in a separate project, although still within a solution in the IDE. Like Android, Windows Mobile xUnit testing also allows for device testing. The greatest difference here, as mentioned above, is the feedback test. Windows Mobile has a full user interface that provides information from each test. This makes it easier for developers to better understand what the test was successful and why a particular test failed.
Debugging support is also important for the development of applications because it is a step in real time by step execution code, which can help you find and correct errors. The treatment process will be dependent on the integrated development environment to carry out its task. Both Windows Mobile and Android step by step debug support platform. In addition, both platforms also include a debugging feature on the device that allows an application running on a mobile device during debugging runs in the IDE.
However, there is a problem with the Android device in the tests compared to Windows Mobile is the readability of the results. Evidence of Android devices do not have a user interface that can display test results. To see the results of the test, a controller that handles the callbacks Android test runner has to be implemented.
Windows Mobile, on the other hand has a high degree of legibility and visibility, while the Android platform is a bit difficult to use when it comes to efficiency. The problem with Android is the lack of information, which is issued automatically through visual tools in the integrated development environment in Windows Mobile.
Windows Mobile implements a version of the xUnit framework. The code for the test class is held in a separate project, although still within a solution in the IDE. Like Android, Windows Mobile xUnit testing also allows for device testing. The greatest difference here, as mentioned above, is the feedback test. Windows Mobile has a full user interface that provides information from each test. This makes it easier for developers to better understand what the test was successful and why a particular test failed.
Debugging support is also important for the development of applications because it is a step in real time by step execution code, which can help you find and correct errors. The treatment process will be dependent on the integrated development environment to carry out its task. Both Windows Mobile and Android step by step debug support platform. In addition, both platforms also include a debugging feature on the device that allows an application running on a mobile device during debugging runs in the IDE.
No comments:
Post a Comment