Knowing what you know
knowing what you don’t know
not having a means to discover what you don’t know
not knowing what means exist to learn what you don’t know
not knowing how knowledge acquisition works
can we answer these questions concretely or only philosophically?
What is quality?
one answer: How well the customer or user of a thing views it as useful/helpful
feels good to use it
easy to operate
know what it can do and can’t do and am happy with that
joy out of using it
customized, personal, based on individual
quality =/= bug-free
one piece of software has a lot of known bugs but is heavily used by thousands or hundreds of thousands of people, another one is bug-free but only used by 10 people, which is higher quality?
The context, its ability to solve a problem in that context,
does it solve the problem in the context in which we’re expecting to solve that problem, without unexpected consequences
chair w/out a seat is low-quality bc you expect to be able to sit on a chair. can’t serve its basic purpose
different chair with seat, but front right leg is 3 inches too short. Leaning back is fine but leaning forward you might fall on the floor. A higher quality chair wouldn’t “crash” like that
how delightful is it to sit in the chair
not just requirements or fitness for use
value to some person
–
what is a test case?
Specific action and outcome
thing u wanna try and a result you wanna verify
ex. post a message to slack, verify it shows up
1 dude argues it’s still one test case if you perform the action and verify the result across different OSes
any time inputs are applied to a program, outputs generated, and a judgment call made.
Judgment call might be different based on context
judgment calls are the hardest part of testing, and it’s based on your own definition of quality
–
what is testing?
1: Investigating, evaluating, learning, sometimes judging?
Vs
2: only judging, that’s what we hire testers to do
1: not only judging: giving new ideas for inputs and outputs
new ideas for tests can follow from results/judgment calls of previous tests
breaking things, discovering where things fail
identifying those judgment calls? The judgments that would put the product at risk
–
what’s a tester?
Keenly focused on risk-to-return
lowering risk on high-value quality propositions
–
what is integration testing?
Making sure all the pieces fit together
the tests you write to make sure other people don’t break you
input, output, judgment call = does your component still return the expected results that my component is counting on?
–
performance testing
inputs and outputs that let you know product is performing as expected
how long actions take in application over a variety of scenarios
key actions product takes and how long each of them takes in different contexts
output = time, judgment = is the time it takes acceptable/good?
Is faster always better? no. only has to be fast enough for the customer
easy to increase performance in the wrong areas. Make the parts that matter fast
From the blog CS@Worcester – Fun in Function by funinfunction and used with permission of the author. All other rights reserved by the author.
