sexta-feira, 24 de julho de 2015

Android Links Research Links

Testing checklist for iOS app


1. Core functionality of the app is working as expected.
2. UI of the app is as expected like all elements are aligned properly; there is no truncation of element or text etc. UI should be consistent across all screens of AUT.
3. Touch area of all touchable elements is big enough so that normal user does not feel any problem in touching them.
4. Font size of all the text should be optimum i.e. neither too small nor too big so that normal user is able to read it with ease.
5. UI remains consistent on rotating the device. If user is reading some text then on rotating device text/list should not scroll to top i.e. it should maintain current position.
6. If on rotating device there is some extra space then elements should be automatically adjusted accordingly i.e. either size of the elements should be increased or other elements (for which user was required to scroll earlier) should be displayed on the screen.
7. Smart phones automatically handle most of the suspend resume functionality automatically but testers should also test it especially in case of audio & video play.
8. If AUT is accessing any third party / inbuilt app like contacts, messaging, email, facebook etc. then it should transfer required data properly and on coming back to AUT should be smooth and should come back to the same screen from where user left.
9. If AUT needs to download very large data then it is recommended to be downloaded asynchronously i.e. initial chunks of data should be downloaded first and user should be able to read text or scroll list while rest of the data is being downloaded.
10. If AUT has some authentication screen like login screen then keep an eye on network log to make sure that AUT does not pass username & password in plain text. Also after logout such authentication tokens / session id should be deleted.
11. If AUT is saving some personal information like authentication token, password, credit card then it should be saved in encrypted form.
12. Instrumentation should be used to check memory leaks and memory consumed by AUT during run.
13.  App should support all the orientation of the device. If not, then both variations of the orientation (in case of portrait mode - upside-down).
14. On uninstalling, all the files related to the AUT should get deleted and other apps should remain unaffected.
15. If AUT displays badge on the app icon then it should display correct count and on every update it should be updated accordingly.
16. If AUT has popover then popover should not have any explicit close button. Instead it should disappear when user taps on any item on it and corresponding action should take place or user tab anywhere else on screen.
17. All navigation should be self-explanatory like Back button should take user to logically previous page, Cancel button should cancel current operation etc.
18. If AUT has scroll-able form like screen then currently focused text field should be visible to user i.e. keyboard should not hide it. And on hiding keyboard screen should be adjusted accordingly.
19. Navigation from one screen to another or screen rotation should not be abrupt. AUT should animate components smoothly.
20. Switching between Wi-Fi and mobile network should not affect functionality of AUT. Also if device’s Wi-Fi and network are disabled by user (i.e. Airplane mode) and AUT tries to make any network call then AUT should be display appropriate error message to user, asking him to enable Wi-Fi. In such scenario AUT should not display loading bar before should error message.
21. Battery consumption should be under control when AUT is running.
22. One of the most important aspects is performance of the AUT. AUT should not be very slow otherwise user will move to other similar apps. AUT should keep user engaged and should display results as quickly as possible.
23. Testing AUT using different network connectivity like Wi-Fi, 3G, 2G etc.
24. AUT should handle network failure scenario gracefully e.g. device loses network while AUT is downloading some content. In such scenario a proper error message should be displayed after timeout i.e. AUT should not keep displaying loading screen indefinitely.
25. Special testing should be done to verify how AUT handles foreign characters and special characters.
26. If new version of AUT is available then user should be notified about the update and AUT should be updated smoothly without deleting existing user’s data and preferences.

Testing checklist for Android app

1. Core functionality of the app is working as expected.2. UI of the app is as expected like all elements are aligned properly; there is no truncation of element or text etc. UI should be consistent across all screens of AUT
3. Touch area of all touchable elements is big enough so that normal user does not feel any problem in touching them.
4. Font size of all the text should be optimum i.e. neither too small nor too big so that normal user is able to read it with ease.
5. UI remains consistent on rotating the device. If user is reading some text then on rotating device text/list should not scroll to top i.e. it should maintain current position.
6. If on rotating device there is some extra space then elements should be automatically adjusted accordingly i.e. either size of the elements should be increased or other elements (for which user was required to scroll earlier) should be displayed on the screen.
7. Smart phones automatically handle most of the suspend resume functionality automatically but testers should also test it especially in case of audio & video play.
8. If AUT is accessing any third party / inbuilt app like contacts, messaging, email, facebook etc. then it should transfer required data properly and on coming back to AUT should be smooth and should come back to the same screen from where user left.
9. If AUT needs to download very large data then it is recommended to be downloaded asynchronously i.e. initial chunks of data should be downloaded first and user should be able to read text or scroll list while rest of the data is being downloaded.
10. If AUT has some authentication screen like login screen then keep an eye on network log to make sure that AUT does not pass username & password in plain text. Also after logout such authentication tokens / session id should be deleted.
11. If AUT is storing some personal information like authentication token, password, credit card then it should be saved in encrypted form.
12. DDMS should be used to check memory leaks and memory consumed by AUT during run.
13.  App should support all the orientation of the device. If not, then both variations of the orientation (in case of portrait mode - upside-down).
14. On uninstallation, all the files related to the AUT should get deleted and other apps should remain unaffected.
15. All navigation should be self-explanatory like Back button should take user to logically previous page, Cancel button should cancel current operation etc.
16. If AUT has scrollable form like screen then currently focused text field should be visible to user i.e. keyboard should not hide it. And on hiding keyboard screen should be adjusted accordingly.
17. Navigation from one screen to another or screen rotation should not be abrupt. AUT should animate components smoothly.
18. It is recommended that AUT should save all large data files on sd card not in phone memory.
19. If app is storing data on SD card then scenarios like SD not available, SD card removed in the middle of data transfer etc. should be tested properly.
20. All the required permissions should be defined in manifest file and it should not have permissions which are not required by AUT.
21. If AUT is a service which gets activated on certain events then those firing of those events should be tested properly. Also if AUT is required to be running in background continuously then scenarios like device reboot, user stops service explicitly should be tested.
22. Switching between Wi-Fi and mobile network should not affect functionality of AUT. Also if device’s Wi-Fi and network are disabled by user and AUT tries to make any network call then AUT should be display appropriate error message to user, asking him to enable Wi-Fi. In such scenario AUT should not display loading bar before should error message.
23. AUT should handle network failure scenario gracefully e.g. device loses network while AUT is downloading some content. In such scenario a proper error message should be displayed after timeout i.e. AUT should not keep displaying loading screen indefinitely.
24. Battery consumption should be under control when AUT is running.
25. Testing AUT using different network connectivity like Wi-Fi, 3G, 2G etc.
26. Special testing should be done to verify how AUT handles foreign characters and special characters.
27. If new version of AUT is available then user should be notified about the update and AUT should be updated smoothly without deleting existing user’s data and preferences.
28. One of the most important aspects is performance of the AUT. AUT should not be very slow otherwise user will move to other similar apps. AUT should keep user engaged and should display results as quickly as possible.




http://cdn.cs50.net/2014/fall/lectures/2/m/lang/pt/


http://bestiejs.github.io/json3/

http://kit.mit-license.org
http://research2guidance.com/

Android InjectView:
http://jakewharton.github.io/butterknife/

MaterialDrawer
https://github.com/mikepenz/MaterialDrawer

Android MP Chart (gráficos)
https://github.com/PhilJay/MPAndroidChart


Android Material Palette Gen:
http://www.materialpalette.com/

Android Material Icon:
https://materialdesignicons.com/

Android Mococa
https://play.google.com/store/apps/details?id=com.desarrollodroide.repos
https://github.com/snowdream/awesome-android
https://github.com/wasabeef/awesome-android-ui
http://www.appbrain.com/stats/libraries



iOS
http://developer.xamarin.com/guides/ios/getting_started/installation/device_provisioning/

iOS Research
http://developer.xamarin.com/guides/cross-platform/xamarin-forms/working-with/listview/
http://developer.xamarin.com/recipes/ios/content_controls/navigation_controller/
http://developer.xamarin.com/guides/android/user_interface/working_with_listviews_and_adapters/part_3_-_customizing_a_listview's_appearance/
http://developer.xamarin.com/recipes/ios/content_controls/navigation_controller/change_the_nav_bar_title/
http://channel9.msdn.com/?wt.mc_id=build_hp
https://icons8.com/web-app/new-icons/all
https://icons8.com
http://www.dummies.com/how-to/content/get-to-know-the-icons-on-the-iphone-status-bar.html
http://blog.xamarin.com/xamarin-events-happening-in-may/


Mobile Templates
http://themeforest.net/tags/mobile%20app
http://myapptemplates.com/
http://www.sketchappsources.com/category/mobile.html
http://developer.android.com/design/downloads/index.html
http://www.smashingmagazine.com/2010/07/14/gcons-free-all-purpose-icons-for-designers-and-developers-100-icons-psd/

Android Package Summary
http://developer.android.com/reference/android/database/package-summary.html

Linux Graphics
https://01.org/linuxgraphics/downloads


Open Street Maps on Android
https://help.openstreetmap.org/questions/13680/how-to-use-osm-in-android-application

Android Livro
http://www.livroandroid.com.br/pages/livro-android.php

Android Tutorial
http://www.vogella.com/tutorials/Android/article.html

Android JSON Parsing Tutorial

http://www.androidhive.info/2012/01/android-json-parsing-tutorial/

Android - Fragments
http://www.tutorialspoint.com/android/android_fragments.htm


Android with SQLite Database Handling in MonoDevelop (Mono for Android, C#)
http://www.codeproject.com/Articles/439852/Android-with-SQLite-Database-Handling-in-MonoDevel



Virtual
https://www.godaddy.com/pro/windows-vps

Dedicado
https://www.godaddy.com/pro/windows-dedicated-server
Growth Hacking


"the right ingredients exist, they just need to be mixed"
plone.org
EAD
Moorc.org
tracegp_abertura
#.tracegp_abertura

https://xamarin.uservoice.com/forums/145075-xamarin-component-ideas
http://www.gsmarena.com/

http://www.nycgo.com/articles/best-nyc-smartphone-apps

http://www.theguardian.com/cities/series/best-city-apps



http://www.summer.harvard.edu/courses/33310


https://play.google.com/store/apps/details?id=tw.com.prolific.app.pl2303terminal
https://pt.coursera.org/
http://www.extension.harvard.edu/academics/courses/courses-by-degree/Software%20Engineering
http://educacao.uol.com.br/album/2012/08/23/saiba-quais-sao-as-20-videoaulas-mais-vistas-no-veduca.htm#fotoNav=10
http://academicpartnerships.uta.edu/apply.aspx
https://ead.upf.br/mod/forum/discuss.php?d=25104
http://ocw.mit.edu/courses/translated-courses/portuguese/
http://www.veduca.com.br/
https://www.edx.org
http://learnsauce.com/googlecloudmessagingtutorial/
http://learnsauce.com/bestPHPprogrammingtutorial/

http://www.codeproject.com/Articles/842041/Sharing-Images-between-Projects-in-Xamarin-Forms
http://www.codeproject.com/Tips/870548/Xamarin-forms-Check-network-connectivity-in-iOS-an



Blogs de tecnologia
http://ziggytek.com/
With an inexpensive USB OTG adapter, you can connect things like keyboards,
 USB hard drives, and even gaming controllers to your Android phone or tablet.,
 BTW Download cool app(s) here:

digger
midiaget


managing media with USB
complex tasks like Android ADB

developing application which exploit the potential of USB framework


using USB Keyboard with Android device without USB host mode enabled and switching from MTP to MSC
USB functions
USB classes available in Android
Chapter 01: Getting Started

Chapter 02: Discovering and Managing USB devices

Chapter 03: USB Storage

Chapter 04: USB tethering

Chapter 05: Android Accessory

Chapter 06: Android USB Audio

Chapter 07: Android ADB

Appendix A: Battery Management

Appendix B: Using Libusb on Android



SOF - start of frame
http://www.usb.org/developers
http://www.telerik.com/purchase/xamarin-ui
https://www.devexpress.com/Products/Xamarin/


Cursos
https://www.caelum.com.br/curso-csharp-orientacao-objetos/
http://www.k19.com.br/cursos/csharp-e-orientacao-a-objetos
http://www.conhecimentodigital.com.br/cursos/curso-de-tecnologia/microsoft-visual-c-net-para-desktop
http://www.codenutz.com/using-dependency-injection-container-xamarin-forms-labs/
http://developer.xamarin.com/guides/cross-platform/xamarin-forms/working-with/databases/
http://www.codenutz.com/using-dependency-injection-container-xamarin-forms-labs/
http://components.xamarin.com/view/sqlite-net/
http://geekswithblogs.net/danielggarcia/archive/2013/12/22/portable-databases-ii-using-sqlite-with-entity-framework.aspx
http://developer.xamarin.com/guides/cross-platform/application_fundamentals/data/part_3_using_sqlite_orm/
http://tableless.com.br/design-para-telas-sensiveis-ao-toque/
http://tableless.com.br/material-design-lite-o-framework-google/

Screen Record Adb
adb shell screenrecord /sdcard/demo.mp4




Postar um comentário