Suggested Topics

If you have any topic suggestions, don’t be shy … let us know about them.

  • Collaborative Work Space field trip
  • Risk Management
  • Event Management
  • Contact Management Software
  • Donors and Donations, eg. CiviCRM
  • Optical Character Recognition – Document archiving, crowd sourcing
  • Finding Things – Search strategies and tools
  • Document Management
  • Encryption
  • Fallout from data breaches
  • Network Security
  • Presentation software

 

Posted in Suggested Topics | Leave a comment

2019-12 — Social — CANCELLED

KWNPSA end-of-year social has had to be cancelled due to unexpected events. We will organize an alternative social sometime in the first half of 2020.

 

Posted in Past Meetings, Social Night | Leave a comment

2019 11 — Friendica

Location: Room 1301 — Conrad Grebel University College, 140 Westmount Rd. N. · Waterloo, ON N2L 3G6 (bottom floor, in the hallway that connects the main building to the Chapel-Residence building)
Date: Monday, 11 November 2019
Time: 7:00-9:00PM

With all of the recent issues going on with social media giants, and, of particular with Facebook, we look to open source solutions where securing data and the sharing of personal data is of primary concern.

One such solution and replacement for FB is Friendica, which has gained some recent popularity. Built along the concept of federated Friendica servers and making use of various protocols such as ActivityPub (formerly ActivityPump from Pump.io), OStatus (from GNU Social) and Diaspora but apparently not Zot (from Hubzilla, which is odd considering Mike McGirvin created both applications); there is a lot to be said about Friendica’s appeal to social media.

On Monday, 11 November 2019, , we welcome Sean Howard who will work us through Friendica’s place as an open source alternative to FB and cover topics such as Friendica’s installation process and ease of server maintenance. We should also have time to cover Friendica’s interoperability with other open source solutions, protocols, data security, etc.

It should make for interesting conversation at a time when seeing social media giants at US congressional and senatorial investigations has now become the norm.

Marc, Steve and Bob

Posted in Friendica, Past Meetings, Social Media | Leave a comment

2019 10 — October Meeting CANCELLED

After much deliberation, we regret to inform you that our next KWNPSA meeting slated for October 21st is cancelled. We had contemplated putting it on, however, the fact that the date falls on voting day for our federal election just complicated matters too much.

Our next meeting will then take place on the evening of November 11th. Although, this falls on Remembrance Day, we could take a couple of minutes at the meeting to recognize those who have and are helping Canada in times of strife, and, in peace.

Our next topic will be posted soon as we are doing a bit of re-jigging of topics.

We will keep you posted as soon as our details are firmed up.

Have a great Thanksgiving Day and don’t forget to vote!

Marc, Steve and Bob

Posted in Past Meetings | Leave a comment

2019 09 The Linux Desktop — A Sensible Alternative to Windows Desktop

Location: Room 1301 — Conrad Grebel University College, 140 Westmount Rd. N. · Waterloo, ON N2L 3G6 (bottom floor, in the hallway that connects the main building to the Chapel-Residence building)
Date:
Monday, 16 September 2019
Time: 7:00-9:00PM

As of the last count for February 2019, NetMarketShare estimates that
Windows’ desktop market share sits at 87.56% worldwide, the rest of the
desktop market share is divided up between macOS – 9.65%, Linux – 2.14%,
Unknown – 0.32%, ChromeOS – 0.32% and BSD – 0.01%.

In September 1991, the Linux operating system was released by its
developer Linus Torvalds. Since that time, Linux has grown steadily into
an operating system to rival all operating systems. Today, the Linux
operating system is core to the Android cellphone system, is used
pervasively in enterprise business and banking, runs government agencies
and powerful science labs. What attracts these large groups to the Linux
operating system is the fact that it is open source and is developed
freely by an army of volunteer developers. In addition, the Linux
operating system is all developed free to use and modify by any
person or group.

For the average desktop user, the Linux system brings some
innovations to the desktop, as well as offers a system that is
largely immune (if regularly updated) to viral and spyware
attacks. By and large, one does not need to install a virus
checker on a Linux desktop, which frees the system from much of
the throttling of CPU speeds usually required by security
measures on the Windows operating system.

For this KWNPSA meeting, long-time member and co-ordinator Steve Izma
will demonstrate that the Linux desktop has all the facilities
needed for a range of users, from those only interested in Web
browsing to system administrators and programmers.

Coordinators:

Bob Jonkman
Marc Paré
Steve Izma

Posted in Past Meetings | Leave a comment

2019 08 Presentation Software

Location: Room 1300 — Conrad Grebel University College, 140 Westmount Rd. N. · Waterloo, ON N2L 3G6 (bottom floor, in the hallway that connects the main building to the Chapel-Residence building)
Date:
Monday, 19 August 2019
Time: 7:00-9:00PM

Are you a visual learner? Are you a visual presenter? Is a picture worth a thousand words? What’s an infographic, anyway? Do you use images to convey ideas? Bullet points? Wall of text? What’s the best way to get your message across? And what do you use to get your message across?

We’ll explore some of the different software available to create presentations.

* Marc Paré will offer a quick demonstration of LibreOffice Impress
* We need someone to demonstrate Microsoft Power Point — any volunteers?

Posted in Past Meetings | Leave a comment

2019 07 LibreOffice User Group

Location: Room 1300 — Conrad Grebel University College, 140 Westmount Rd. N. · Waterloo, ON N2L 3G6 (bottom floor, in the hallway that connects the main building to the Chapel-Residence building)
Date:
Monday, 15 July 2019
Time: 7:00-9:00PM

Does your organization write documents? Work with spreadsheets? Create graphics? Make presentations? Do you use an Office Suite of applications? Do you need support for your Office Suite? Do you use Free/Libre and Open Source Software? Would you like to put all this together?

Welcome to the Inaugural Meeting of the LibreOffice User Group!

KWNPSA/NetSquaredKW will host a LibreOffice representative to discuss plans for establishing a local LibreOffice community group. Then Marc Paré, a long-time member of KWNSPA who also volunteers for the LibreOffice Foundation will make a presentation about the LibreOffice organization and member-based meritocracy.

Together we’ll establish a common monthly date and place where members would meet so the LibreOffice User Group can get underway for August.

And, of course, we’ll have our round-table problem-solving discussion on all things related to LibreOffice and User Groups.

–Marc Paré, Steve Izma & Bob Jonkman

Meeting Notes

Marc Paré showed a slide presentation on the creation of the LibreWaterloo Community Group

  • What is “The Document Foundation” (TDF) and how does it relate to the LibreOffice opensource office suite
    • The Document Foundation” was created with the “objective of the promotion of office software available for use by anyone free of charge.”
      Built on the concept of “meritocracy”.
      “The Document Foundation is a charitable Foundation under German law, founded on February 17th, 2012. Its objective, as defined in the statutes, is to nurture and develop office software that is free to use by everyone. The foundation furthers a sustainable, independent and meritocratic community which develops free, libre and open source software based on open standards through international collaboration.
      We are driven by thousands of volunteers as well as paid contributors worldwide, and with joint forces, provide the best free office suite, LibreOffice, which is available in over 110 languages, for any major platform.
      Our values are openness, transparency and meritocracy. By using these as our guiding principles, we have made our budget as well as our financial reports public.” (LibreOffice Download Page) [see: https://www.documentfoundation.org/foundation]
    • Board of Directors https://www.documentfoundation.org/governance/board/
  • The TDF is parent organization to 2 projects: LibreOffice Project and Document Liberation Project
    • Document Liberation Project [https://www.documentliberation.org/]
      • The Document Liberation Project aims to attract developers from all corners of the FOSS world to join with the LibreOffice developers, strengthening existing relationships and forging new ones with all who have shared goals in the domain of file formats.The Document Liberation Project exists to provide a home for the growing community of developers united to free users from vendor lock-in of content. It aims to contribute to the flourishing Open Document eco-system by providing powerful tools for the conversion of proprietary file formats to the corresponding ODF format.
    • LibreOffice Project [https://www.LibreOffice.org/]
      • is an opensource office suite
      • has over 120 million users at last approximate count
      • has had over 1000 developers work on the code
      • has many community groups organized on all continents except for Canada and US
      • supports over 110 languages and growing
      • available for many platforms, of note: MSWindows, Mac, Linux, SunOS, FreeBSD, OpenBSD, NetBSD etc. [https://wiki.documentfoundation.org/Documentation/System_Requirements]
      • code is developed from group of volunteer-coders from all over the world
      • manuals/books/marketing/user support/ etc. are all run by volunteers
      • very few paid staff, most are related to infrastructure to maintain servers
        • some staff for marketing, localization …
      • holds a yearly conferences [https://www.LiboCon.org/]
      • LibreOffice Videos
        • LibreOffice General Over-View https://www.youtube.com/watch?v=3KC0ZdcA6s8
        • LibreOffice 6.0 New Features https://www.youtube.com/watch?v=YHBve8v13VY

“LibreWaterloo” (LibreOffice Community Group)

  • As LibreOffice Canadian users, we would like to contribute to the LibreOffice Project and have a local presence on the Canadian scene with respect to the LibreOffice Project and software
  • We would like to connect with local LibreOffice coders and users alike
  • “To have fun” should be one of the pillars and principles we strive for in the organization

Proposal of Activities to Undertake

  • Hold regular monthly meetings where LibreWaterloo organization business is discussed
  • Present LibreOffice-related news or usage
    • Demystify user-related questions with LibreOffice
  • Promote ODF format in Canada
    • Government
    • Education
    • Private Enterprises
    • * Note that TDF has joined OASIS in furthering the development and promotion of the ODF platform. It is now a major active member.
  • Organize LibreWaterloo Hacker/Bug Fests; QA Fests; conferences
    • Participate in local/away Canadian/US conferences where TDF/LibreOffice presence may be pertinent
    • Maintain the LibreOffice conference kit
  • Documentation help with LibreOffice guides and books
    • Cooperate with local University/College technical writing programs/classes and develop formative technical writing sessions using the LibreOffice guides/books as working examples
      • Getting Started with LibreOffice Guide
      • Writer
      • Calc
      • Impress
      • Draw
      • Base
      • Math
      • Logo
  • Spearhead Indigenous language preservation through the Localization Team
    • Seek partnership with the First Peoples’ Cultural Council (http://www.fpcc.ca/)
    • Seek governmental grant applications to help notarize various local indigenous languages in LibreOffice in partnership with Canadian Indigenous stakeholders
  • Help contribute to the LibreOffice project
    • Code contribution
    • Choose an aspect of LibreOffice that is under-serviced and contribute in a concrete way, such as specialize in Accessibility contributions
    • Accessibility code contribution
    • Accessibility QA
    • Accessibility User Experience
    • List and testing of compatible tools in the area of accessibility
    • Software compatibility
    • Hardware compatibility
    • canvass/approach hardware manufacturers and seek hardware donations to the community in order to test it against the use of LibreOffice
  • Assist the LibreOffice Project where possible
    • Attend Canadian, US conferences as per request for help from the TDF/LibreOffice Project
  • Assist and promote LibreOffice ecosystem start-up organizations
  • Eventual goal of incorporating under charitable organization
    • Could Help collect any donation to the main LibreOffice Project with receipt
    • Would permit application to government grants for future projects
    • Web Presence
      • Maintain LibreWaterloo web sites, such as website; Twitter, Facebook; mailing lists etc.
  • LibreWaterloo members should strive to gain membership with the LibreOffice Project but not required to belong to the LibreWaterloo Community group
    • ** Note – to become a member of the TDF·LibreOffice Project requires non-trivial contribution in some aspect of the project over the period of 3 months’ activity and recognized by the LibreOffice community and membership. Thereafter one may apply to become a member of the TDF/LibreOffice in good standing. [https://www.documentfoundation.org/governance/members/]

For more information or to join the community

Marc Paré
623 Bluenose Crescent
Waterloo ON
N2K 4H4

Cellphone: 519-744-9396
marc.pare@librewaterloo.ca
marc@marcpare.com
marc.pare@libreoffice.org
https://www.parEntreprise.com

Posted in LibreOffice User Group, Past Meetings | Leave a comment

2019 06 Agile vs. Waterfall

Location: Room 1300 — Conrad Grebel University College, 140 Westmount Rd. N. · Waterloo, ON N2L 3G6 (bottom floor, in the hallway that connects the main building to the Chapel-Residence building)
Date:
Monday, 10 June 2019
Time: 7:00-9:00PM

Do you manage projects? Software development projects? Are they big projects or small projects? Are there many or few developers? Is it complex software or easy to understand? Are you developing for external customers or your own organization? Are there many opportunities for testing or only a few? Can you develop new code while testing, or is development dependent on test results? Are transient coding errors tolerated or not? Do you need Agile or Waterfall Development?

Let’s discuss different coding methodologies with an expert in the field. Perhaps you are that expert!

–Marc Paré, Steve Izma & Bob Jonkman

Meeting Notes

  • Introductions

Guests:

    • Eric Gerlach is a senior director at Netsuite
    • Darcy Casselman is a senior developer at Netsuite and organizer with MakerExpo
What is TechSoup?
  • Software distribution company, many different vendors
    • Microsoft, Netsuite, Adobe, &c.
    • TechSoup matches NonProfits with vendors, manages licenses, ensures non-profit registgration status
    • Why not free (no cost)? TechSoup still has costs, and license payments ensure less proliferation of unlicensed software
Introduction to Agile Development
  • Book by Gil Broza, a local Canadian “Agile Luminary” — The Agile Mindset
  • The Agile mindset (not the book) has become less “elite”.
  • Traditional development techniques give you what you asked for, not what you wanted
    • Also gives you nothing until the project is entirely complete
  • Donald Rumsfeld’s “Unknown Unknowns” — he was so right when it comes to software development (not so much for political situations)
  • Agile Mindset — Values:
    • People first, before product and process
    • Adaptation
    • Early and frequent value delivery
    • Customer collaboration
  • Agility is not the perfect solution for every situation, it is a way to achieve a certain goal.
  • Waterfall Mindset — Values:
    • Make early commitments
    • Get it right the first time
    • Deliver on time and on budget
    • Process comes first, before product and people
  • Government is super waterfall! (experienced voices who have worked in government concur)
  • Is Agile vs. Waterfall dependent on the size of the organization?
    • Maybe true for government, is it true for very large organizations?
    • Agile interaction enhances the skill set of the people
    • Corporate (and Government) management styles have not kept up with management styles in project management
    • But eg. Amazon’s software development process, including budgeting, is very agile
    • We don’t know what a fully Agile large corporation would look like (yet)
    • Is the budget process responsible for process-bound governments and corporations? eg. yearly budget cycle, or based on 3-4 year election cycle.
    • Failing frequently: Better to fail at ten different $100,000 points in the project, rather than once at $100,000,000 point in the project
  • Graf von Moltke: “No plan extends with any certainty beyond the first contact with hostile forces”
    • So you want to build in a much higher ability to adapt, revise quickly, learn quickly.
  • Classic Waterfall failure: Government of Canada’s Phoenix payroll system
    • In spite of rollout problems on the first day, the rollout was continued (no adaptation)
    • The first year (2016) cost of failure was $50,000,000. Still ongoing today.
    • Payroll in insanely complex…
    • Netsuite’s HR and payroll software is aimed at smaller businesses, not something the size of Phoenix
  • Risk-based development: Riskstorming (like brainstorming for risks)
    • Risk mitigation strategy: Ask for e-mail address (or money) before a product exists (ensures there is interest in the project, and worthwhile continuing)
    • For non-profit orgs, a small financial outlay may be overwhelming, so do risk mitigation
  • 68% of IT projects fail
    • Traditional response: Plan more! More detail! (costs & time increase)
  • People First: Theory X and Theory Y
    • Motivation (external, internal)
    • Responsibility (none, lots)
    • Money (only important thing, not as important as doing good)
    • Non-profits tend to fall into Theory Y
  • Software development is a people skill
    • Diagnosing personal interactions to build better software
    • Software development is a team sport (esp. in large organization)
  • Early and frequent value delivery — What is “value”?
    • Early startups doing things that don’t scale, eg. AirBNB using paper forms for client matching
    • But they’re delivering value, not software
    • Other examples of manual processes that eventually automated, a la Mechanical Turks
  • Agile has frequent points of value delivery, even if the cost of that value is less than the cost of the development to that point
    • Eventually, the value exceeds the cost (at the completion of the project)
  • Does modularity have anything to do with it, rather than monolithic design?
    • Modularity goes to frequent value delivery, and smaller costs of failure
    • Modularity goes towards the people thing, since people can work more autonomously
  • Philosophy of design has been around for a long time, not solved yet.
    • Modular vs. monolithic
    • These days the monolithic design is pushed to the side
    • Sometimes companies discard monolithic design too quickly
    • Advantage of monolithic: There is only one thing to manage!
  • Customer Collaboration
    • Google Wave: A solution to a problem that didn’t exist
      • Had they talked to anyone, they might have realized no-one wanted it
    • Color photosharing app
      • No-one understood how it worked
      • Could have been the results of a requirements document: “The program must do this thing” and it does, but…
  • The customer is a member of the development team
    • Traditional picture has the customer sitting beside the developer
    • Constant communication!
  • What’s the difference between Agile and a mini-Waterfall approach?
    • As the Waterfalls become smaller and smaller they begin to look more like Agile
    • But Agile still needs customer consultation, iteration, value delivery
    • An overall Waterfall approach could still have Agile at the micro level
  • What do we give up with Agility?
    • Predictability, lower cost, no rework, uniform work processes, comfort, consistency, easy thinking
    • and break-neck speed development
  • Agility requires more creativity, waterfall can rely on rote work
  • Agile is not “better, faster, cheaper”, it is only “better”
    • Perhaps in the long run it is faster and cheaper too
  • Agile requires developers’ self-examination, looking at yourself as working in a team
    • This is hard, not everyone is successful
  • Project manager: Maybe lose some velocity if you’re delivering the right thing.
    • Working faster may deliver something faster, but is that the right thing?
  • Detailed mockups get less demanding feedback from customers
    • Back-of-napkin designs may get criticized for small details, not relevant to the issues you’re looking for
  • Project management tools like Timeline and MS-Project tend to encourage Waterfall approaches to projects
  • Tools for Agile Project managers:
    • Trello (small, super simple, basically free)
    • JIRA (pretty heavyweight)
    • Rally (not recommended)
    • Pivotal Tracker
    • TAIGA (Open Source)
Posted in Agile, Past Meetings, Waterfall | Leave a comment

2019 05 Education

Location: Room 1300 — Conrad Grebel University College, 140 Westmount Rd. N. · Waterloo, ON N2L 3G6 (bottom floor, in the hallway that connects the main building to the Chapel-Residence building)
Date:
Monday, 13 May 2019
Time: 7:00-9:00PM

Is your Non-Profit an educational organization? As its main function? Or is teaching one of many services you offer? What do you teach? How do you teach it? Do you have classrooms? With computers? What software do you use for teaching in the classroom? Do you have online courses? What online software do you use online? How do you establish your curriculum? How do you perform evaluations? How do you track student progress? Do you work with other educational institutions? Other certifying agencies? What constraints to they impose on your teaching programs?

We’ll have a demonstration of Moodle by Marc Paré and perhaps a representative from KW’s Desire To Learn. And, of course, we’ll have a Round Table discussion on how each of us are managing our organizations education needs.

–Marc Paré & Bob Jonkman

Posted in Education, Past Meetings | Leave a comment

2019 04 Software Testing

Location: Room 1300 — Conrad Grebel University College, 140 Westmount Rd. N. · Waterloo, ON N2L 3G6 (bottom floor, in the hallway that connects the main building to the Chapel-Residence building)
Date:
Monday, 8 April 2019
Time: 7:00-9:00PM

If you work in software development, how much of your job involves testing? If you’re a project manager, do you work closely with the testers to keep an eye on their results and bug reports as a project progresses? If you are a developer, do you do your own unit testing and work with testers on test plan reviews and fix the bugs they find when they do integration and regression testing? If you are a software tester, how do you balance the need to be thorough with the need to deliver on time? How does that affect writing test plans? When a project team has to deal with a lot of changes in the middle of development and testing, how do you cope with updating test plans with limited time? Since you should be considerate when reporting bugs in software, especially when people have worked hard on it, how can you do this tactfully? How do testers work with people like technical writers who use test plans as a reference when writing documentation like user manuals?

Nicholas Collins, a long-time member of KWNSPA and a professional software tester will give us an overview of the deep art of testing software.

— Bob Jonkman & Marc Paré

Resources

One of James Bach’s talks on YouTube

Meeting Notes

  • Introductions
  • Nicholas Collins
    • Software tester for a few years, knowledge of how his company works
    • But two years isn’t a long time compared to some software testers
    • Nick has prepared notes, will be presenting slightly differently from other KWNPSA sessions
    • SysAdmin in insurance industry; laid off (as are many of us); back to school to upgrade IT skills
    • Uses Visual Studio, C#, other languages
    • People he’s met were developers, or business-specific skills; when software testers are needed these people are thrust into the role
    • This might change as more universities offer software testing as a major
    • There are very few courses or certificates in software testing, more prevalent in the US
      • but Fanshawe college in London has a certificate program
    • Some institutions have a couple of courses in tech writing, project management, quality management; maybe a night course in software quality testing
    • Without academic rigour, different people use different terminology, nomenclature
      • “Should I know what all these different terms mean?” But it’s fairly common with other software testers Nick has spoken to
    • At Microsoft, developers use their development skills to write tests. Needs more skills than just coding
      • Microsoft has internal courses to train testers how to test software
      • Get promoted to full developer once you’ve proven you can write tests
    • people use Terminology like “Post-mortem” (although nobody dies), mix up “Milestone” and “Benchmark”, &c.
    • Software testing is the start for a developer’s career, then to DevOps
      • Does this mean the most junior, inexperienced programmers are responsible for testing software?
    • Nick: large companies use junior testers to run tests, senior testers to supervise
    • During an upgrade Nick (a programmer at the time) did testing for the Database Analyst
      • But a junior intern was assigned to that role as well, just to gain experience.
      • Worked out details at a high level, then applied tests to get results
  • Project Managers take different approaches
  • You can always think of more tests
    • It’s a fine balance between staying on schedule and being thorough
    • Walkthroughs and working in a team can be helpful
  • Some testing instructors do not like teaching from texts
    • eg. “Software Testing” by Yogesh Singh
    • But Nicholas gets good ideas from texts, doesn’t agree with those testing instructors
    • THe problem is that the authors suffer from “Perfect Worldism”
      • A world where there is unlimited time and money, and the perfect tests can be developed
    • Nicholas has experience with sticky problems, gets ideas from texts to adapt to his problem
  • Even the simplest test “is A < 70 ?” can have seven or eight tests
    • Test results, but also overflows, boundaries, different data types
    • Input validation can require many tests
  • Working with other people, eg. technical writers
    • For them to understand the software they’ll play with the software, and may create unanticipated conditions
    • Everyone can be a software tester to some degree: Project manager, developer, writer. Even sales?
    • Sometimes testers find problems with usability as they’re running tests; not part of the test suite
  • How effective are some of these ad-hoc testers?
    • Is there a bias? Do they have some incentive to pass tests even when there are problems?
      • Sometimes a QA will hold back tests that would have been better to give to the developer in the first place
    • Accessibility testing is a new skill for QA, may become a testing requirement
    • Business Analyst (BA), developer and tester make a good team
      • Sometimes the process of testing will identify the need for more testing
  • Reporting bugs
    • Requires consideration, tact
  • Test plans may need to be developed quickly
    • But near the end of a project when time is tight there may not be time to develop tests
    • So quality of code may suffer near the end of the project
      • Breaking things during testing that no-one has time to fix
  • Automated testing?
    • Nick has experience with automated regression testing
    • Automated regression testing reduces the introduction of new bugs
  • Open Broadcaster Software
    • Used to catch all activity during user testing
    • Also use Virtual Box recorder uses host to capture all the output on the VM screen
  • “Monkey Testing”
    • Also “fuzz testing” or “fuzzing”
    • Fill all fields, try to overflow, pound on the keyboard, click as fast as possible
      • But this this does not lead to reproducible errors (fine timing errors)
      • Although some testers claim they can reproduce
  • Pride in finding bugs?
    • Nick finds that the “high five” time should occur only after the entire team has identified, reported, documented, and fixed the error, and re-tested
  • Load testing
    • Hitting a system with a large number of transactions, &c.
    • But a bogged down system may not be writing to logs, making analysis difficult
    • A benefit in load testing is adding assertions, find issues with threads
      • Assertions and Singletons…
    • Be sure to validate the output even when just testing for capacity
  • Nick has written a test for XML testing
    • But the code Nick wrote was not well tested at all! Oh, the irony!
  • Q: Do you use debugger software like GDB to examine the flow of code?
  • A: Not common, but becoming more prevalent.
    • Certainly having a debugger to throw at the code is nice to have
    • But much testing is done with the software under test as a black box, just examine the input and the expected output
  • Nick speaks of the complexity of software testing.
    • One thing works fine by itself, and other thing does too, but do they work together?
    • Different software on different platform needs to interoperate, but sometimes differences in date formats causes problems
      • although each platform by itself passed all tests
    • Dealing with currencies, eg. USD and CAD, and GBP
    • Dealing with leap years and 29 February
    • General rule: Anything date sensitive needs to test for leap years
      • and time zones! Anything dealing with calendars needs to worry about time zones
  • What happens internationally when different countries need to interoperate?
    • Companies have service contracts that define how the service is implemented
      • If the system is changed, the contract defines who is responsible for continued interoperation
      • If I make a change and it breaks your system, it’s your fault for not defining the contract accurately
      • called “spring contracts”
  • Nick gives an example from James —- YouTube video (“nominal input voltage is 100VAC to 250VAC”)
    • “Test the nominal range” is an incomplete answer
    • Also need to test outside the range
    • The user manual may give advice not to go outside the nominal range, but users don’t necessarily read the manual
    • So, does the system fail gracefully outside the nominal range?
    • This is the function of the software tester, to design the test to ensure that software or equipment is failsafe
      • eg. for medical equipment
      • How much money is available to fry the device under test? Some prototypes may be really expensive
      • Many examples of people damaging electronics with incorrect application of voltage!
    • It’s good for testers to think outside the parameters of the system
  • Testing to ensure system has a consistent look and feel
    • eg. fonts on some menus were different
      • Is that a software testers responsibility? Sometimes as an additional task
      • There are tools (overlays, templates) to find these issues
    • Window resizing can make the application fail, but there need to be limits for those tests
    • Testing for “greyed out” functions can be time consuming
      • When a function is available when it shouldn’t be can result in errors
    • These are general things for a tester to keep in mind
  • Systems that have features which have little to do with each other
    • Easy to test they’re not contending for resources, &c.
    • But still important to run these features simultaneous to shake loose bugs, eg. memory allocation, concurrent DB access
    • Perhaps a simple monitor with limited functions: But what if something goes wrong, does the device report an error?
  • Client-side data validation: All testing needs to be duplicated at the server to ensure malusers don’t bypass client-side validation
    • But that increases load on the server
  • Logging
    • Logs may indicate problems with the way the code executes, eg. repeated log entries indicate an invalid loop
    • Circular reasoning: How can the logs from software under test be considered
      • Logs are only one step, begin the process of analysis
      • NewRelic will test user experience (surveillance software)
  • Nick has found bugs because the test suites are well designed
    • But at least half the time the bugs discovered were found in spite of the test, which was not designed to find that kind of bug
  • Q&A
    • Is the developer + tester model usable?
      • May be a bit scary for shops not set up for that collaborative arrangement
    • Nick says to just forge ahead.
      • Having experience is good, but can also develop that experience in-house
    • Worries about the coming requirements for accessibility for software
      • May take changes in coding practices (use POSH: Plain Ol’ Semantic HTML instead of Javascripted forms)
      • Jurisdictional differences may be difficult to deal with
Posted in Past Meetings | Leave a comment