The Red Earth QA SIG is an Information Technology organization that focuses on improving the quality of software implementation projects by sharing information on testing tools and techniques. This also includes networking with peers that may or may not be full-time Quality Assurance staff.
Thursday, December 16, 2010
Tips for moving from Agile to Waterfall
Tuesday, December 14, 2010
Tips for moving from Waterfall to Agile
This site requires a free registration to access.
Here is a summary of the three issues that come up
- Task Size and Frequency
- Documentation
- Scoping Discussions
The article seems to be a balanced view of the differences with good tips on becoming agile successfully.
Sunday, November 07, 2010
Today in Computing History
https://sites.google.com/site/todayincomputinghistory/
Thursday, November 04, 2010
How does User Experience and Agile interact?
Tuesday, November 02, 2010
New scripting environment for UI testing - Sikuli
http://groups.csail.mit.edu/uid/sikuli/
Friday, October 29, 2010
Free StarWest Virtual Access!
https://event.on24.com/eventRegistration/EventLobbyServlet?target=registration.jsp&eventid=239875&sessionid=1&key=7C4552EDC5D391DB815FD6223C1C630A&sourcepage=register
Wednesday, October 27, 2010
Worse Than Failure
Microsoft Web Application Configuration Analyzer
Stupid DNS tricks - Saving/Loading Data
Tuesday, October 12, 2010
No Good Deed Goes Unpunished
- 'For where's our blessed " status quo," '
- 'A just Deed in the world ? — call out the rifles !'
Monday, October 11, 2010
Book Review - Software Engineering Best Practices
Thursday, September 09, 2010
Free ebook on Computer Security
Thursday, September 02, 2010
Google Code University
http://code.google.com/edu/courses.html
Here is a sampling of the courses offered
Programming Languages Web Programming Web Security Algorithms
Enjoy!
Wednesday, September 01, 2010
Monday, August 30, 2010
Software Test Automation Workshop - September 14-15
The main objective of this course is to help you understand the landscape of software test automation and how to make test automation a reality in your organization. You will learn the top challenges of test automation and which approaches are the best ones for your situation, how to establish your own test automation organization, and how to design software with test automation in mind. You will also learn many of the lessons of test automation by performing exercises using sample test automation tools on sample applications.
You will leave the course with your own test automation strategy and plan for implementing it.
GSA discount available. Contact us for information.
This workshop will be held at:
Hampton Inn, Airport South
1905 South Meridian Avenue
Oklahoma City, Oklahoma,
USA, 73108-1719
1-405-682-2080
Thursday, August 19, 2010
Webinar: Fundamentals of Complete Crash and Hang Memory Dump Analysis (Second Session)
Information and Registration for the Webinar
Monday, August 09, 2010
Replica of an early computer
Tuesday, August 03, 2010
Coding skills
http://sixrevisions.com/resources/10-puzzle-websites-to-sharpen-your-programming-skills/
MD5 checksum is good, but not foolproof
http://www.mscs.dal.ca/~selinger/md5collision/
Monday, August 02, 2010
But I already learned that...
Thursday, July 22, 2010
Memory Dump Analysis Book
http://my.safaribooksonline.com/9780955832802
Those of you with ACM (and possibly IEEE) memberships may already have access to this online.
Monday, July 19, 2010
How to be a programmer - One person's perspective
I ran across this the other day. It's old, but it does describe some skills that are not often discussed.
Thursday, July 01, 2010
More ways to learn about computer security
Tuesday, June 29, 2010
Test your code online!
Tuesday, June 22, 2010
Interesting debugging technique for windows
If you have a MSDN license, you can get what's called the 'checked build'. This is a build with debug messages enabled and optimizations turned off. It's most useful for debugging device drivers, but it can help replicate timing issues with the kernel since the timing will be different than for the retail version. Rather than having to install each component from the checked build, you can limit it to a couple files files. The instructions below show how to install and set up your system to have a boot option for this.
Obtain the checked build
http://msdn.microsoft.com/en-us/library/ff549603(v=VS.85).aspx
Install minimal comonents from the checked build
http://msdn.microsoft.com/en-us/library/ff547196(VS.85).aspx
Especially if you are tracking down timing issues, this may expose the issues more clearly.
Monday, June 21, 2010
Barriers to Automation
Here are some of the scenarios that have come to mind based on what I've seen:
- Someone takes the inititative to create a set of tests, but other priorities take them away and the tests become obsolete, making them nearly useless.
- We bring in a contractor to build tests, but when the contract is over, there is nobody given the responsibility and the time to keep them up.
- We start some UI automation testing and find that the scripts are fragile, making upkeep difficult and ultimately are left to become obsolete.
This is not to say that we don't have some successes with automation:
- There are many experiences of using throw-away scripts to perform some focused and repetative task.
- There are internal tools built to assist with generating data.
- Development teams have their own scripts / applications for performing installation/configuration/cleanup tasks.
The trick is to see the pattern with the successes and failures.
Successful attempts at automation seem to have these common qualities. They typically are either grassroots efforts where time is found to work on them or they are given priority by management to spend on them. Grassroots efforts typically have modest upkeep costs and time can be found for upkeep. Management-directed efforts have had continued priority set for them since they require much more upkeep. Grassroots projects are typically used heavily by internal staff and Management priorities are typically used outside the development teams (including other internal teams as well as customers). Your experiences may differ from these as these are based on my own observations.
Unsuccessful attempts at automation appear to have these in common. There was no call to maintain the time needed to maintain these scripts either from the grassroots level or from management. The scripts were succeptible to changes in code, operating system, 3rd party components such as browsers, Java, .NET, Application Server Versions, etc.
So how do we take advantage of the things that make these efforts successful and mitigate the things that make them unsuccessful?
Auutomation has to be something that is used regularly. Whether it's an expectation of your development process or a commitment made to have time spent on upkeep during a project, it can't be an afterthought.
The benefits of automation must be valued both at the grassroots level and by management. I see that in both cases, I generally see agreement that automation is helpful, but I think there may be different ideas on what that looks like. Having this be very visible and openly discussed will contribute to it's long-term success.
Environment and code changes that affect scripting should be mitigated. Managing unit tests over time is a difficult process when the library of unit tests becomes large. Not only do they take time to run, they need to be managed and 'sunset' just as we would do for any other piece of code. There needs to be a lifecycle for these tests that address 1)When they should be built 2)How long they should be maintained 3)When they should be removed from use. UI tests are much more succeptible to these environmental changes. For example, different operating systems render web pages as well as applications differently, making some UI tests suitable for cross-platform execution difficult or impractical. Using 3rd-party UI components require customized tools to use for automation, often at additional cost. These additional tools are not absolutely required, but they do help with not only automating the tests, but also in validating the results. These UI tests also need to have a lifecycle with the same requirements as for Unit Tests. While UI tests are helpful, there needs to be more scrutiny applied to what tests get automated and in what environment(s).
Now what?
"It depends". Much of what needs to happen must be based on your circumstances. What is the will internally to make changes? How far does this will go to ensure that these changes are implemented for the long-term? What resources are available to impelement these? What training is needed? Once you start to answer these, the answers will become more clear.
Book Review - Little Brother
Essentially, this is a fictional account based in many topics related to security (physical, computer, privacy, etc.) and a series of events that affect these. A seventeen year old boy and his friends are caught up in a terrorist plot by being in the wrong place at the wrong time. What follows is a drastic shift in what various governments and other groups consider 'acceptable levels of monitoring' and what it means to those being monitored and those doing the monitoring.
What strikes me most is the main character's internal monologue on the effectiveness of different security measures. In some cases, they just make everyone feel more secure, but do little to address true risks. In other cases, the data gathered starts to be misused, prompting the question "Who is watching the watchers?".
This book is an easy and excellent read. It's entertaining and thought provoking. You may even learn a thing or two. I certainly am. The book can be purchased and it can also be downloaded in several electronic formats for free.
Wednesday, May 26, 2010
Analyzing dumps
Automate Changes to web.config files for unit testing ASP.NET Web Services
Monday, May 24, 2010
Summer Hiatus for Meetings
Friday, May 14, 2010
Better Software in 60 Seconds, #1
Tuesday, May 11, 2010
Open Source Load Testing Tool
Friday, May 07, 2010
Google's Website Has Vulnerabilities (and they want it that way)
Monday, April 19, 2010
On-line demos for Unified TestPro manual and automation testing tool (please RSVP)
Manual tool demo; 9am and 11am CDT, April 21st, or 11am CDT April 23rd
Automation tool demo; 9am and 11am CDT April 22nd, or 3pm CDT April 23rd.
GoToMeeting or GoToWebinar format.
This will be an RSVP event. Information will be provided upon RSVP.
James Wright jwright@okc.sdtcorp.com
General Manager, Test Service Operations
Software Development Technologies
405-232-6000 x.11
405-232-6008 Fax
580-641-1360 Cell
Tuesday, April 13, 2010
Online Demo of Unified TestPro, Friday, April 23rd
Tuesday, April 06, 2010
International Symposium on Functional Programming (in Norman)
My Article on Software Quality History
Monday, April 05, 2010
Test Coverage Technique
Tuesday, March 30, 2010
The Good, The Bad and The Ugly of NTFS Alternate Data Streams
A file stream is essentially metadata added to a file that doesn't interfere with the contents of the file. One way to see this data is to look at the 'Summary' tab of a file.
But as you can see, the comments section in particular can be quite lengthy. Note that not all file streams appear here, others may be included. Also, the space used by the file streams is not used when calculating the file size, so adding more data to the ADS does not change the size reported by the OS.
This method is also used in other ways. Icon files are associated with the URL shortcut files for IE as a file stream and the blocking of downloaded files from execution is handled through ADS. Microsoft provides a tool to let you find files that have streams attached to them. You can read about it here http://technet.microsoft.com/en-us/sysinternals/bb897440.aspx
The Bad and The Ugly
This method can be used to make both text and binary files difficult to find. It's even possible to use the command shell to make an executable file (such as notepad) an ADS for a pre-existing executable (such as the calculator application), rename the executable and run it! This sample screenshot shows what happens when notepad.exe is added as an ADS called 'runtime.exe' to the calc.exe file and is executed. In this case, the notepad executable is being run from the runtime.exe ADS for the calc.exe.
Fortunately, you see the shenanigans when looking at the task manager. Also, all of these activities require someone with sufficient permissions. This means, that your system would already have to be compromised for this to happen.
Monday, March 29, 2010
Practical Software Test Automation Course - Oklahoma City, May 13 & 14, 2010
Understanding Computers from 'first principles'
Wednesday, March 17, 2010
Meeting Announcement- Evening Meeting 4:30pm-6pm Thursday, March 25th
- We're moving to evenings to accommodate your busy work schedule!
Time and Location
We will be meeting at the FIS/Metavante offices at 1200 Sovereign Row. The meeting is from 4:30pm to 6pm.
Topic
Directions
- From I-40, take Meridian South
- Turn Left at Will Rogers Parkway
- Turn Left at Sovereign Row
- The FIS/Metavante offices are on the right just before the curve in the road.
Wednesday, March 03, 2010
Tuesday, March 02, 2010
Charles Babbage's connection to the Luddites
Monday, March 01, 2010
The Rule of 1000 Decisions (as a tie into myth-busters)
Thursday, February 25, 2010
Who Says Writing Documentation is Dry?
Wednesday, February 24, 2010
Free Seminar on User Stories, March 2nd.
Tuesday, February 23, 2010
Follow Us On Twitter!
@redearthqa
Friday, February 19, 2010
My Review of "Modeling Software Behavior"
If you haven't been there, it's an excellent resource for not only book reviews :) , but also lots of other information on tools and techniques. This is produced by the same company that puts on The Star Conferences.
http://www.stickyminds.com/s.asp?F=S1203_BOOK_4
Tuesday, February 16, 2010
New Meeting Location for February.
- From I-40, take Meridian South
- Turn Left at Will Rogers Parkway
- Turn Left at Sovereign Row
- The FIS/Metavante offices are on the right just before the curve in the road.
Monday, February 15, 2010
Meeting Announcement- Evening Meeting 4:30pm-6pm Thursday, February 18th
- We're moving to evenings to accommodate your busy work schedule!
Time and Location
The Red Earth QA's meeting will be held on the 3rd floor of 100 N. Broadway from 4:30pm -6pm on Thursday, February 18th. Look for the signs to direct you to the correct room.
Topic
Directions
- You can park in Main Street Parking on Main or you can find street parking.
- From I-40, take the Robinson Exit. Go North on Robinson to Main. Right on Main. You can either go to Main Street Parking or continue to Santa Fe Parking. You will see 100 N Broadway on your left across Broadway. The building says 'Chase' at the top.
Tuesday, February 09, 2010
Was your last project successful?
Friday, February 05, 2010
Online UI Mockup Tool
A small company called Balsamiq is making an online version of their product to create screen mockups available.
http://www.balsamiq.com/demos/mockups/Mockups.html
It pops up a dialog every 5 min or so to suggest using a paid version. Even if you don't get licenses for this, it may be useful for small projects.
Details of the features are here:
http://www.balsamiq.com/products/mockups
Thursday, February 04, 2010
Agile Technique Proposed in 1968
"The paper presents a method of modelling a computer system design as it evolves, so that evaluation can be made an integral part of the design process. The paper introduces the concept of concurrent existence, within a single model, of several representations of the system being modelled, at differing levels of abstraction. Thus important design decisions are expressed directly in terms of appropriately abstract quantities, facilitating understanding, validation, and modification of the system design. The paper includes brief details of an experimental implementation of the modelling technique and of the use of the technique to model both hardware and software components of a multi-processing system."
Monday, January 25, 2010
Thursday, January 21, 2010
Meeting Announcement- EVENING MEETING! 4:30PM-6PM, Thursday, January 28th
- We're moving to evenings to accommodate your busy work schedule!
Time and Location
The Red Earth QA's meeting will be held on the 3rd floor of 100 N. Broadway from 11:30am-1pm on Thursday, December 17th. Look for the signs to direct you to the correct room.
Topic
Bring your test plan template and compare with other companies.
Directions
- You can park in Main Street Parking on Main or you can find street parking.
- From I-40, take the Robinson Exit. Go North on Robinson to Main. Right on Main. You can either go to Main Street Parking or continue to Santa Fe Parking. You will see 100 N Broadway on your left across Broadway. The building says 'Chase' at the top.
Friday, January 08, 2010
Wired Magazine - "Software Flaws Let Christmas Bomber Get Through"
Monday, January 04, 2010
Project Management, 60s style
What I originally found amazing is that it's a fairly sophisticated view of project management. The first chapter is particularly enlightening since it discusses the inspirations for the methods detailed in the book. Basically, there was research from as far back as 1896 on streamlining production processes that are being applied to research in the late 1950s that culminated in the findings described in this book.