I love it that in Windows you can do everything both by mouse and keyboard.
Take the start screen: there are 3 ways (mouse only, mouse + keyboard, keyboard only) to zoom in/out in the start screen. Read the rest of this entry »
Test Dummy: returns nulls (or equivalents null) to consumers as they should not have used: the dummy is a filler in the parameter list to setup the System under Test.
Test Double: the generic term (sometimes informally called mocks, but they are not; see Test Mock below).
Test Stub: like a Test Dummy, but returns a specific value for a specific test (or group of tests). For instance return true for a LoginStub.
Test Spy: like a Test Dummy (or evenTest Stub) but also makes a note (or log) of each call (so you can spy on the calls). It can lead to coupling, so might make your tests fragile.
Test Mock: like a Test Spy, but allows verification of certain existence of absence notes or log entries (called Expectations). Like ensuring a certain call to theTest Mock was made with certain parameters.
Test Fake: unlike a Test Stub, as fakes have business-like behaviour (so it simulates business behaviour to a certain extent, for instance by having certain data-sets in memory, or responding with certain business logic for instance returning true for certain Login conditions). It also means thatTest Fakes need unit tests of their own.
The links in the above list all contain a small diagram showing the dataflow between the Test Double, System under Test, stc. Jeff Atwood has some nice graphics to go with them at Test Doubles: A Taxonomy of Pretend Objects.
In practice, Stubs and Spies are probably used most, followed by Mocks (either in code or with a Mocking tool).
Notes:
The above order is how the story explains them, not the list by Martin Fowler or the list on WikiPedia.
Make sure you download the 1.6.1 version as that is really the latest:
SourceTree 1.6
Enhancements
All new file status view
Improved diff view
New view configurations
Cleaner user interface
All new welcome wizard
SourceTree 1.6.1
Bugfixes
SRCTREEWIN-1902: Fix crash bug when trying to create a new repo from hosted repos screen
SRCTREEWIN-1915: Fix a rare crash bug which could happen when closing/re-opening a repository
SRCTREEWIN-1894: Staging/unstaging will get ‘stuck’ and not refresh the file list if you turn on ‘always display full console output’ when performing these operations. The refreshing now happens regardless of whether that option is turned on or not.
SRCTREEWIN-1897: Fix a crash bug when listing Stash repos from hosted repos list.
Confirming removing files now shows the file names in a list so you know which files you’re removing
SRCTREEWIN-1909: Can now commit files if committing individually even if they’re at the root and not using staging (so either Mercurial, or no staging mode in Git)
Line 1 gets the CFE bootloader version
(1.0.2 and lower boot with 32K of NVRAM, 1.0.3 and up with 64K of RAM; some Firmwares work around the 32k limitation)
Line 2 gets the Firmware model and version
Line 3 gets the CPU speed
Line 4 and 5 get the temperature for eth1 (2.4 Ghz) and eth2 (5 Ghz) in Celsius
It is based on the RMerlinDev (firmware developer) information on temperatures: These are for each radio. Take the returned value, divide by 2, then add 20. Results are in Celcius.
Next to that knowledge, it uses a few tricks on awk calculation, and first parameter in awk (the second parameter would be the hex value of the temperature code in parenthesis) which is easier than shell calculations.
Based on those, I found a few very useful scripts: