Difference between revisions of "Software Testing"

From SOBAC Wiki
Jump to navigation Jump to search
(Add link for TechSoup Catalogue)
(Moved Resources to Meeting Notes)
 
(8 intermediate revisions by 3 users not shown)
Line 2: Line 2:
 
<!-- Entity for colon needed so it's not interpreted as <dt> by wiki -->
 
<!-- Entity for colon needed so it's not interpreted as <dt> by wiki -->
 
; Date: Monday, 8 April 2019 Year from 7&#x3A;00pm to 9&#x3A;00pm <!-- {{ical|url= xxxxx-Meetup-iCAL-URL /ical/topic.ics }} -->  
 
; Date: Monday, 8 April 2019 Year from 7&#x3A;00pm to 9&#x3A;00pm <!-- {{ical|url= xxxxx-Meetup-iCAL-URL /ical/topic.ics }} -->  
; Meetup Event: xxxxx URL to meetup.com
+
; Meetup Event: https://www.meetup.com/NetSquared-Kitchener-Waterloo/events/260073069/
 
; Location: Room 1300 -- Conrad Grebel University College, 140 Westmount Rd. N., Waterloo, Ontario {{map|url=https://osm.org/go/ZXnbg2DSE--?m=}}  
 
; Location: Room 1300 -- Conrad Grebel University College, 140 Westmount Rd. N., Waterloo, Ontario {{map|url=https://osm.org/go/ZXnbg2DSE--?m=}}  
 
<!-- ; Event Announcement: [[xxxxx Page Name/Announcement xxxxx YYYY-MM-DD]] --> <!-- URL for the announcement message sent a few days before the meeting -->
 
<!-- ; Event Announcement: [[xxxxx Page Name/Announcement xxxxx YYYY-MM-DD]] --> <!-- URL for the announcement message sent a few days before the meeting -->
  
Does your Non-Profit Organization use software? Does it work the way your staff expects? The way your clients expect? How can you be sure? Do you write in-house software? Does '''that''' work the way you expect? How do you know? Do you have separate Development and Testing and Staging and Production environments? How do you test software, anyway?
+
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.
 
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.
Line 16: Line 16:
  
 
* [[Software Testing/Meeting Notes 2019-04-08]]
 
* [[Software Testing/Meeting Notes 2019-04-08]]
 
==== Resources ==== <!-- move to Meeting Notes after the session is held -->
 
 
[https://www.techsoupcanada.ca/en/directory/334 TechSoup Canada catalogue: Developer Software]
 
[http://example.com/link Link Text]
 
 
[http://example.com/link Link Text]
 
 
  
  
 
[[Category:NPSA]]
 
[[Category:NPSA]]
 
[[Category:Events]]
 
[[Category:Events]]

Latest revision as of 22:10, 27 April 2019

Software Testing

Date
Monday, 8 April 2019 Year from 7:00pm to 9:00pm
Meetup Event
https://www.meetup.com/NetSquared-Kitchener-Waterloo/events/260073069/
Location
Room 1300 -- Conrad Grebel University College, 140 Westmount Rd. N., Waterloo, Ontario Map

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é