Production deployment starts with the first line of code: an application should be built to work in production infrastructure, could be deployed using existing process, be it CD or manual update and handle load expected in production. Even in almost ideal CD process with wide use of automation where it is possible, some human interaction might be required when it comes to changes to DB, build scripts or infrastructure with new release.
A placebo is designed and used primarily for psychological benefit. Things like sugar pills, elevator door close buttons, and office thermostats aim “to please”, rather than have any other, “real” effects. Now, consider a placebo in the context of software and testing. What if “pleasing” is the only intended and expected result? How can it be tested? What does a bug look like? And, do these ideas also apply to non-placebos that have other, “real” effects? In this workshop, we’ll explore placebos, nocebos, the placebo/nocebo response, illusion and locus of control, relativism, wants, needs, and expectations, and will connect it all to testing.
In an increasingly hypothesis-driven product development world, experimenting with Minimum Viable Products (MVPs) is considered as a pragmatic approach towards building the eventual “1.0” product. MVPs allow the team to systematically validate its key hypotheses, and create a basis for making critical product decisions based on evidence from the field. In this webinar, we shall examine the theory behind testing your MVP and describe a few of the popular testing methods. We shall also consider real-life examples to illustrate the point.