Anyone here a Software Tester?

Hi all.....I'm wondering if anyone out there knows about software testing. I need to test the application I support as we've got some new features in the Permissions module. My problem is that I don't know how to make sure I cover all aspects of the module.
The way the application is set up, we have the main Users/Group module which obviously has the various Users and Groups. Then we have Permissions, which are modules and tabs within the module that are then set as Read, Read/Write, or Forbid. We have over 30 Modules, each module containing up to 50 possible tab/subgroup to be tested, so I fully expect this to be a complex task. Finally, we have Secured Controls, which are specific fields, drop boxes, searches, etc. that we can set permission to. There's over 170 of those.
I have a fairly good idea of how I want my groups to be set up, but I haven't written anything down yet as I'm a tiny bit overwhelmed and not entirely sure where to start. I've looked at a bunch of testing sites but haven't found anything on testing permissions.
Really appreciate any suggestions you have.
Thanks in advance!
Chris

 

How can we get to know more about the application? Is there a homepage?

 

Hi Cordialis and Plodr,
Thanks for the replies. No homepage, as it's an application used within only my group. It's developed by a third-party developer, so I have no input or visibility to the code (I believe that makes the testing I'm doing "black box" but I'm not sure of the terminology). The application is being used right now by 350+ users in my company, and has been for about three years. I am in the group responsible for supporting the application, as well as report development, data analysis, documentation of the application, etc. etc. so I'm all to aware of the issues. I have set up an access database to track the bugs I report, and our developer uses their own system to log the issues (they are a well-established development company here in Canada). My boss has asked me to review the permissions, as there have been some changes made and we need to verify everything works. Let me give an example so that things may be a little clearer:
- There are modules in the application for the Contracts, Vendors, and Product Codes for all companies my group deals with.
- Each vendor has between 1 and 7 contracts with us, and each contract has multiple product codes
- Each product code represents a specific work function, with the unit of measure being standard and the unit cost changing.
- Within the Contract Module, I can access the Product Codes available to that Contractor, as well as transmission information, and territory they cover
- Right now, if I set a User with Read-Write to the Contract, they have access to *everything* within that module, even if I set the Product Code module as Deny, because the user can access it through the Contracts module.

What I'm trying to figure out is how I can make sure I cover all possible variations of permission levels and do the appropriate testing so that issues like the example above can be caught and addressed. I will probably need to use an Excel spreadsheet to track my findings, but I don't know how I should be reporting these issues back to the developers so that it makes sense.
Apologies for the rambling, I just woke up and haven't had any coffee yet.
Thanks for the help.....
Chris

 

What qualifications do you expect from the beta testers? Or what would make them interested in your product? What kind of user group do you need? Multimedia people? Security freaks? Designers? Office people? And what's in it for them? What support can you offer them if the beta program causes problems?

 

And what's the program about anyway? A game? Mail? Learning CSS? The weather? How to loose weight?

 

Hi Cordialis,

It's not that I'm looking for beta testers - we have no money in the budget to pay anyone else. It's going to be me doing the testing - I have some experience with this as I've been doing it from day 0 of the application project, but I've been limited to testing the application itself, not the security and permission levels.

The application is huge - it's a contract management application where we give work to our third-party vendors, give permits to contractors to enter our worksites, track damages to our facilities, import all requests for utility locates from 3 provinces, etc. Unfortunately I can't give any more information than that as it would involve me giving out confidential information, but that's the gist of it.

Thanks,
Chris

 

Well, now your postings actually makes sense. :-D It is not a program all these vendors and contractors are going to sell. This is about management and organizational theory in a software form. :cool Inter-organizational development, partnerships and online networking.

 

Yeah, that's it. I'm so used to explaining the application to people in my company that I forgot how to relate to normal people! I'm a tool. I need more coffee...cup number 3, here I come.

 

You have reached the point where administrative sciences are taking the focus and the software part is less important. The build/development is ready for beta testing. Frankly, this is not the forum for that kind of research.

Managing supply chains, logistics, external control of organizations, J. Pfeffer, G. Salancik, H. Minzberg, W.R Scott and what have we. That's the stuff you need to get under your belt.

And here we are at Majorgeeks talking about games, drivers, Java, Vista and XP Home. I'm afraid that users who happens to know about the topics you have precented would only be in here by coincidence. If I knew about an excellent management forum that would suit your needs I would gladly give you a link but I don't. My guess is that the response you're looking for should be found elsewhere.

Frankly. And I'm sorry for it. But I honestly think it is so.

 

Hey Cordialis - Appreciate your response. Figured it was a shot in the dark but there's no harm in asking. I have posted my question on a couple of Testing forums and QA sites, and I'm just waiting to hear back (much smaller user base = longer wait times). I will therefore return to my perusing of the software thread and see what other useful info I can uncover.
Thanks again,
Chris

 

What about a forum for management students?

 

I worked at usability testing co. years ago, think you need to narrow it down. There are some guides on the net and really no way to test everything a user can do, so give yourself a break.

http://software.gsfc.nasa.gov/AssetsApproved/PA2.5.1.3.pdf
3.1.1 Task Definition, old but basics are the same.

Some good task info:
http://software-testing-zone.blogspot.com/2008/06/what-to-test-pareto-analysis-high-risk.html

http://www.geocities.com/xtremetesting/
http://www.dmoz.org/Computers/Programming/Software_Testing/
http://www.softwaretestingsucks.com/
http://www.softwaretestingwiki.com/doku.php?id=communities

Well the good news is you have 350 in-house testers (if you can use them all), I would break them into groups of 5 to cover as much area as possible.

Groups 1 – 30, Limited user, modules (accounting, inventory, merchandise ...) = 150 users
a-p test functions then break that down to modules by user.

Group 1Acct = Limited user, Dept Accounting, Module(s): Accounting, Customer Service, Purchasing, Inventory
(Alice, Joe, Bob, Steve and Lupe) would have limited tasks:
a. Find customer order status
b. Find cost info
c. Find last invoice from XYZ vendor
d. Access secure area...just a test, should not be able to do.
e-h. Everyday tasks (whatever they do)
i-m. Test new features or changed features
n-p. Test access, security, see if they can read/write what they should not be able to.

Groups 2-30 would have similar tasks for limited user level and their module(s).

Group 2 Invt = inventory module, limited user
Group 2 Mrch = merchandise module, limited user

Next Group 31-50 = 100, average users; test write permissions, input, data retrieval, reports for this level

Next Group 51-60 = 50, advanced users, test access levels, test data transfers, reports, advanced tasks etc.

If you have more permission levels, make more groups but narrow it down; think it should go by permission levels but you could also do it by Module. Maybe you're getting overwhelmed with the permissions in the module, not all users have access to all modules. i.e. Inventory can't access accounting, accounting can't move inventory but advanced user can adjust/override the cost. Our depts have access per user level to different modules and permissions but might not be the same for your co.

Not sure what your biggest user group, guessing limited is. Talk to one actual user at every permission level and module. I could tell you in 5 min. my most often used features in every module, then easy to develop tasks. Also, put everyday tasks scattered in tasks so users do not get frustrated with harder tasks or tasks they can't complete. Inform them that not all tasks can be accomplished it's a test of the software not them. Make users comfortable as possible when testing, stressing them out corrupts your test. Do not react or tutor when a user can't perform a task that they should be able to do - move on.

You don't need as many testers as you go higher up the permission ladder, user group is fewer and module access greater. Also since most advanced users have access to multiple modules they might need more complex/combined module tasks.

I would add QA group of Advanced users to test the Limited, Average users...sometimes they see what others miss. Dept. Managers could do this. This can be done afterwards, does not have to be done at the same time.

We used a spreadsheet to track bugs, was basic QA by module, issue, follow up, assigned to/date, status. Regretfully I tossed my usability manual awhile back and pc that had it is long gone.

Some ideas, someone here was looking for this type of tracker awhile back...can't remember outcome, hopefully someone will know.

http://office.microsoft.com/en-us/templates/TC010785151033.aspx?CategoryID=CT101481361033
http://office.microsoft.com/en-us/templates/TC011926911033.aspx?CategoryID=CT101481361033
http://office.microsoft.com/en-us/templates/results.aspx?qu=issue+tracking&av=TPL000

It seems overwhelming till you break it down, since I'm not familiar with your software this is the best I can do from a rusty memory, hope it helps. Take a step back, have a friend not involved look at criteria, it will give you a fresh look at things.

 

Hi Cat w 9 lives,

Thank you so much for the time it took to reply - you are a champion among Geeks!

I spoke with my boss about having some of the users provide information for permissions, testing etc. and his response was to laugh. He said given what he's seen with the groups as he's been going around the province, he wouldn't trust most of them with more than a plastic spoon. He's also made it very clear we have no resources, so I'm in on this by myself.

I've read over the links that you provided - man there's a lot of information. But I will be taking your advice again and break things down into small, manageable pieces.
Thanks again......
Chris

 

Hi Chris, your mgr is a dork, sorry.

A system this complex could/will cause a problem. I work with modules all day, not doing testing of users is a big mistake IMO. Even with a knowledgeable person setting up our system and QA I find errors... someone puts something in inventory that is not there *poof* there goes 30K. Buyer sets costs wrong *poof* there goes the profit margin. Knowledgeable people make mistakes everyday, even with checks in place so not testing users on a system is dangerous IMO, you can't do it all.

Our system can send a test module to a user and no harm done, great for testing users but not sure if this is available to you, if so you have a argument for testing your users.

Looked at our modules today, separated into headings...customer service, accounting, inventory, purchasing, board is vast and then 5-10 modules plus the sub ones per heading...maybe testing per Heading/Module would be easier with limited resources.

Regretfully the IT guy that set up our system QA is gone and not available for me to tap. Bad timing because he made me look like the little geek I am, he could make short work of this. I tested end user software (all-in-ones, graphics, websites...) not operating systems where I worked and just going by what I see now and past.

Bottom line is we had 10 employees, tech consultants - if needed, plus all the resources of a major company and min. of 15 testers in the last stage just testing end user software. If we had to test something this big we would have added consultants out our wazoo to start the project.

Don't let the dork get to you, you can do this when you break it down. Will take more time with limited resources but doable and don't lose any sleep over it, your manager isn't. You're a better geek than him any day, you know when you need help, he's clueless!

 

Hey Cat (if I may be so bold with the informality )

Once again thanks for the reply. I did in fact lose sleep over this last night, so reading your post this morning made me feel a whole lot better (and your usage of dork made me laugh - been too long since I've heard that word!).

Today's project is making a list of the items I want to test, and then setting a realistic timeline for them so I know ball-park how long this whole thing's going to take. If my boss is available today, I'm going to take this to him and basically say "Ha! You expect me to do all of this by myself while doing everything else you throw at me!?" (granted, he may say Yes, but I'll pass out when and if we cross that bridge).

OK, time for me to start working. NO, first - coffee. Then a nap, check my email, go for another coffe, THEN work.