Profile

Cover photo
Gabriel Weis
Works at Velosys GmbH
Attended MSc. Computer Science
Lived in Darmstadt
260 followers|5,102 views
AboutPostsPhotosVideos

Stream

Gabriel Weis

Shared publicly  - 
 
So I combined two passions of mine, cycling and Android. And here's the result ;-)

www.velosys.de
4
4
Ovidiu Latcu's profile photoZeljko Kovacevic's profile photo
Add a comment...

Gabriel Weis

Shared publicly  - 
 
 
Today’s #AndroidTools #Protip from +Stephan Linzner is about android test size annotations and finding the right size for your next test.

Android test size annotations let you classify how long a test should take to run, and consequently, how frequently you can run the test. The annotations are defined in the android.test.suitebuilder.annotation package. To use one of the test size annotations @SmallTest, @MediumTest or @LargeTest simply annotate your test methods with the appropriate annotation, i.e. 

@SmallTest
public void testFoo_bar() { … }

A Small test should take milliseconds, a Medium test a couple of seconds, and Large several minutes. To make decisions easier here are some additional guidelines you can use to find the right test size next time you write a test.

@SmallTests 
Execution time: < 100ms, these tests should be run very frequently.
Focused on units of code to verify specific logical conditions. These tests should runs in an isolated environment and use mock objects for external dependencies. Resource access (such as file system, network, or databases) are not permitted. Tests that interact with hardware, make binder calls, or that facilitate android instrumentation should not use this annotation.

@MediumTests 
Execution time: < 2s, these tests run at least on every check in of your code.
Focused on a very limited subset of components or a single component. Resource access to the file system through well defined interfaces like databases, ContentProviders, or Context is permitted. Network access should be restricted to localhost only and (long-running) blocking operations should be avoided and use mock objects instead. Note that any child of InstrumentationTestCase is at least medium!

@LargeTests 
Execution time: < 120s, these tests should be run as often as practical. At least once a day.
Focused on any or all application components and subsystems. These tests fully participate in  the system and may make use of all resources such as databases, file systems, and network services. As a rule of thumb all external communications such as GPS, Bluetooth, Radio, and Telephony must be large tests. Most functional UI tests, that test across multiple components, are also large tests too.

Well organized tests suites using test size annotations can improve your efficiency and productivity and establish a common understanding within your team on when to use the right test annotation for the job. Think about it when you are writing your next test. 

If you want to learn more about Android Testing and how to run specific test suite for a given size, please visit: http://developer.android.com/tools/testing/testing_android.html and http://googletesting.blogspot.co.uk/2010/12/test-sizes.html.
1
Add a comment...

Gabriel Weis

Shared publicly  - 
5
Moritz Post's profile photoGabriel Weis's profile photoDirk Sagwitz's profile photoRonan Schwarz's profile photo
4 comments
 
Hmm, I think this feature should be used to make a backup of the users app settings not of his content. This is a nice feature if it succeeds but not a no-go if it fails.
Add a comment...

Gabriel Weis

Shared publicly  - 
 
GIT branch model

http://nvie.com/posts/a-successful-git-branching-model/

Thank you to Michal Harakel who pointed me to this interesting article!
3
Add a comment...

Gabriel Weis

Shared publicly  - 
1
Jens Becker's profile photoMichal Harakal's profile photo
2 comments
 
Don't want to...
Add a comment...
In his circles
307 people
Have him in circles
260 people
Miguel Ruiz's profile photo
Harry George's profile photo
Bridget W's profile photo
Holger Kramer's profile photo

Gabriel Weis

Shared publicly  - 
 
 
Today’s quick #AndroidDesign #Protip from +Christian Robertson and +Nick Butcher is about keeping your animations snappy.

Animation can bring an app’s UI to life, communicate important information and help to maintain context. Slow animations or too much movement however can be distracting. Instead, use an abbreviated animation to suggest a larger movement.

For example, the Android keyboard appears to pop up & fade in from the bottom of the screen when you focus an editable field. This large movement could become tiresome and slow the user down from performing their goal: actually entering data. To prevent this, we skip the first 80% of the animation and simply show a translation and fade for the final 20% of the animation. This small animation implies a larger one but keeps it snappy.

That’s it for today but chime in in the comments with any questions or related tips.
1
Add a comment...

Gabriel Weis

Shared publicly  - 
 
You want to connect your Android to your car?

Duncan J Burrell!
3
1
Gabriel Weis's profile photoMichal Harakal's profile photo
2 comments
 
Oh, how could I oversee this? The Master has arrived :-D
Add a comment...
People
In his circles
307 people
Have him in circles
260 people
Miguel Ruiz's profile photo
Harry George's profile photo
Bridget W's profile photo
Holger Kramer's profile photo
Work
Employment
  • Velosys GmbH
    CEO & Co-Founder, 2011 - present
  • Android Software Engineer
    Freelancer, 2009 - present
Places
Map of the places this user has livedMap of the places this user has livedMap of the places this user has lived
Previously
Darmstadt
Links
Story
Tagline
Software Engineer, Android Enthusiast
Education
  • MSc. Computer Science
    Application Development, 2009
Basic Information
Gender
Male