RStudio Desktop Pro
Test connecting to a license server
Everything passed—great! All done.
…Then I felt like entering a negative number.
Valid ports values go up to 65535 (2^16 - 1)
Negative numbers wrap around like a dial1
Why would you enter a negative number?
Why would you enter a negative number?
Because you can.
Why would you enter a negative number?
Because you can.
\(\Rightarrow\) Need to be aware of & handle improbable cases so that RStudio doesn’t break.
This was an example of
manual exploratory black box testing.
This was an example of
manual exploratory black box testing.
This was an example of
manual exploratory black box testing.
This was an example of
manual exploratory black box testing.
Compare toexploratory Scripted = detailed test cases based on specs.
Or, perhapsmanual Automated = predefined & run automatically (!)
Stumbles across strange and interesting problems
Stumbles across strange and interesting problems
Some more Desktop Pro license testing
…and unplugging the cable from the wall.
Testing
Testing
by
Testing
by
i.e. dogfooding
Then suddenly, while poking around,
files stopped opening on Ubuntu.
Sometimes.
RStudio Server
Files Pane
Mac
1.2.695
Open File
Windows
1.2.679
Ubuntu
Red Hat
1.2.707
SUSE
1.1.453
RStudio Desktop
Behavior was complicated by:
Behavior was complicated by:
Behavior was complicated by:
Behavior was complicated by:
Behavior was complicated by:
Behavior was complicated by:
Once the cause & resolution were identified, validation was a little easier
The arrows lined up