* uses java’s proxy feature
* covers one of junit’s weaknesses
* “recording” required
* useful for jdbc testing
* needed in what kind of unit testing scenarios
“mock objects can simulate the behavior of complex, real (non-mock) objects and are therefore useful when a real object is difficult to incorporate into a unit test.”
=> For FTTP testing, it might help when u need a “mock iview object” ie a mock object in place of the real iview
“multiple assertions” are a common topic among Junit users — “it’s not important to have precisely one assert per test; many experienced testers have multiple assertions in a block at the end of a test method.”
Q: what if you have an alias, a shell func, a shell built-in (like “echo”), a unix executable file, and your own script all sharing the same name?
Focus on 2 simple rules for now:
1) Your own aliases override everything else (such as shell functions)
2) $PATH is the very last (after things like shell built-in commands) place searched by the shell. Executables in $PATH are external to the shell.
I think the same precedence holdes for any shell.
I helped research and design a similiar technique for a high-scalability, modern system. My technique is more REAL than a pool of threads that you shift and allocate among applications.
Do you know what it was? hint: 2006 Mansion
A: 32-cpu solaris box T2000
#1: squid cache
#2: a single mysql master replicating to multiple slave machines
exactly as advised in [[ programming php ]]. Other interesting tips:
#9 job queue for mysql operations
beside processor cores, physical RAM was allocated to applications, too, in my Mansion data center.
db connection obj
db connection set-up
jdbc conn pool
simple? Is shell scripting simple?
These tend to be interview questions, because
* most of us are expected to have used them or know them well
* => yardstick to measure and compare candidates
* familiar to most interviewers