Risk based domain analysis of one OOo variable, for BBST Test Design Assignment 3

3 December 2011 01:09 pm
adric: (nuts)

A follow-on to the risk catalogue from previous assignment and DW post. Again here is a messy blog post on methodology and what the cat was doing (yowling) while download LibO to my iMac and as I struggle to put together the formal report specified in the assignment.

LibO lastName entry points

I started off this morning at the VW dealership with some exploratory testing to see if any of the spare few test ideas I have noted are feasible/sensible. I quickly realized a few key things. To keep my test case collection manageable I should probably settle on one or at most two ways to input values of the variable under test. In my initial risk catalog write-up (cf prev post) I identified three major entry points: start-up wizard, options, read from user settings.

( goes on for quite a bit, it does )

Some notes on tools

While blundering around I found many better ways to do what I was up to. Even without a formal harness it's easy to generate and evaluate data against a SUT this way with the built-ins of any scripting language. I settled on Python because after trying some Ruby and Perl I got going the fastest in Python .. though as I found easily enough I was still going much slower than I needed to. I should have googled sooner as that would have saved me some time and keystrokes.

Here are two things I will use in the future for this sort of exploration: Python libraries to interact directly with the platform clipboard and (if available) the Ruby black bag security toolset. There's no coincidence at all that the same tools that work for neutral/academic software testing and QA are also used to attack software and find its weak point and I've studied both.

Ed note: I've submitted the assignment to the class and will post it here after the course is done and grading is completed.

Tags:

Test Design Lab: technique attributes

19 November 2011 05:48 pm
adric: books icon (c) 2004 adric.net (Default)
If the core attributes for test design in scenario testing are Appropriate complexity, credibility, motivation, validity and value and the desirable characteristic is ease of evaluation , then I'd say:

The core attributes for function testing are coverage, validity, and affordability. Desired characteristics of a function test (plan) are performability and reuseability. Function testing considers whether individual functions (features, groups, of functions, etc) are performing correctly and function test plans are usually based on covering all of the functions adequately with tests. At such a small scale validity is very important for function tests or they have little value. Function testing can be automated which may reduce costs. Automated function testing can be implemented into development procedures (as unit testing often is) which allows for reduced cost through reuse. The test suite can assert that the operation fo the functions tested is unchanged after changes to the SUT by developers.

The core attributes for risk based test design are credibility, information value, motivation, and power and a desirable characteristic of risk test is affordability. Risk based testing seeks to find potential failure modes fo the SUT, produce them, and gather information about their likelihood and consequences. Good risk based test design should find demonstrable bugs which case noteworthy failures in the SUT including failures that may affect other systems. These tests should help convince stakeholders to make needed changes based on the potential risks identified and demonstrated. Risk based testing can vary in it's application between quicktests which are effective for certain common failure types to more complex and expensive failure mode analysis such as that performed by engineers in safety industries.

Core attributes of specification testing are accountability, coverage, and value. Often specification testing is for purposes of determining compliance with formal specification which may have legal weight. In these cases the details fo testing may be published or even be part of the public record through a standards body or court proceeding. In these cases coverage of the entire formal specification by the test plan is completely required and the information gathered is of considerable importance to the organization running the tests. Other kinds of specification testing, such as competitive product analysis, also provide good value to the testing organization.
Tags:

Applying the HTSM to the Google Presentations manual

16 November 2011 08:00 pm
adric: books icon (c) 2004 adric.net (Default)
From the online manual for Presentation and relevant sections of the main Docs manual  we can harvest about 36 declarations of features which are mostly Functions in Product Elements:
  • Share presentations with your friends and coworkers. Upload and convert existing presentations to Google Docs format.
  • Download your presentations as a PDF, a PPT, or a .txt file.
  • Insert images and videos, and format your slides.
  • Publish and embed your presentations in a website, allowing access to a wide audience.
  • Draw organizational charts, flowcharts, design diagrams and much more right within a presentation.
  • Add slide transitions, animations, and themes to create show-stopping presentations.
  • See exactly what others are working on with colorful presence markers
  • Edit a presentation with other people simultaneously from different locations
  • Use revision history to see who made changes or to revert to earlier versions
  • Say hello, start a conversation or share new ideas using built-in chat
  • Create Google documents, spreadsheets, other file types, and collections.
  • Upload (from your computer, if you'd like), manage, and store files and folders.
  • Share Google Docs, files, and collections.
  • Preview your docs and files before you open or share them.
  • View images and videos that you've uploaded to your Documents List.
  • Search for items by name, type, and visibility setting.
  • Convert most file types to Google Docs format.

  • Add flair and format your documents, with options such as paint format, margins, spacing, and fonts. 

  • Invite other people to collaborate on a doc with you, giving them edit, comment or view access.
  • Collaborate online in real time and chat with other collaborators.

  • View your documents' revision history and roll back to any version. 

  • Download Google Docs to your desktop as Word, OpenOffice, RTF, PDF, HTML or zip files.

  • Translate a document to a different language.

  • Email your documents to other people as attachments. 

  • Share and edit presentations with your friends and coworkers. 


  • Import and convert existing presentations in .ppt and .pps file types. 


  • Download your presentations as a PDF, a PPT, or a .txt file.


  • Insert images and videos, and format your slides. 


  • Allow real-time viewing of presentations, online, from separate remote locations.


  • Publish and embed your presentations in a website, allowing access to a wide audience. 

  • Share and edit drawings with your friends and coworkers.

  • Download your presentations as a PNG, JPEG, SVG, or PDF file. 


  • Insert images, shapes, and lines, and format them to fit your preferences. 


  • Real-time collaboration with other people, no matter where they are. 


  • Insert a drawing into a document, spreadsheet, or presentation.

We can infer these details about the environment and delivery of the product from the application and the feature list:
  • Presentations is an online application and runs in a web browser and on Google servers.
  • Presentation requires Internet access to Google servers and other Internet resources for full use of features.
  • Presentations accepts file upload from the web browser in certain file formats and outputs files.
  • Presentation files may also be embedded into other web sites.
  • Presentations uses Google's shared user authentication and authorization systems and Google search.
  • Presentation is free to use  without charge for anyone with a Google account.
and so fill in some other details of the Product Elements:
  • Structure: and Operations: Presentations is delivered as a online service (SaaS) and there is no physical product.
  • Platform: Google's platform is used for (at least) storage, authn, authz, search, revision control, machine translation, document format conversions,  and application delivery.
  • Data: Presentations reads in and writes out in multiple well-documented formats and also has an internal format.
We can also fill in some information about possible Operational Quality Criteria.
  • Compatibility: Presentations reads and writes multiple file formats besides it's native data format.
  • Compatibility: Presentations is sensitive to web browser feature levels.
  • Installability criteria may not be applicable since Presentation is delivered as a service
  • Security in Presentations is implemented with features of Google hosting services and may not be directly testable.
  • Capability: A serious failure or lack of any of the features bragged about in the manual will strongly impact quality
Tags:

Profile

adric: books icon (c) 2004 adric.net (Default)
adric
adric

May 2025

S M T W T F S
    1 23
45678910
11121314151617
18192021222324
25262728293031

Links

Syndicate

RSS Atom

Most Popular Tags

Page Summary

Style Credit

Expand Cut Tags

No cut tags
Page generated 17 June 2025 02:02 pm
Powered by Dreamwidth Studios