The online community for software testing & quality assurance professionals
 
 
Calendar   Today's Topics
Sponsors:




Lost Password?

Home
BetaSoft
Blogs
Jobs
Training
News
Links
Downloads



Quality Engineering >> Requirements and Design

Pages: 1
aadi
Newbie


Reged: 12/23/06
Posts: 11
Manual testing
      #462866 - 03/01/08 05:17 AM

At what point in the testing process is it possible to generate a report that demonstrate the number of conflicying requirement?

Post Extras: Print Post   Remind Me!   Notify Moderator  
Joe Strazzere
Moderator


Reged: 05/15/00
Posts: 12344
Loc: Massachusetts, USA
Re: Manual testing [Re: aadi]
      #462879 - 03/01/08 07:04 AM

aadi - Is this an interview question?

--------------------
- Joe
Visit AllThingsQuality.com to learn more about quality, testing, and QA!

I speak only for me. I do not speak for my employer, nor for anyone else.


Post Extras: Print Post   Remind Me!   Notify Moderator  
prabakar_prabu
Member


Reged: 03/12/07
Posts: 131
Loc: India
Re: Manual testing [Re: Joe Strazzere]
      #463307 - 03/04/08 02:02 AM

aadi,
after the Requirement study is completed then you produce the report
or
after finished the walkthrough,Inspection then you produce the report

Regards
prabu


Post Extras: Print Post   Remind Me!   Notify Moderator  
Joe Strazzere
Moderator


Reged: 05/15/00
Posts: 12344
Loc: Massachusetts, USA
Re: Manual testing [Re: prabakar_prabu]
      #463365 - 03/04/08 04:36 AM

Once you know and understand all the requirements, then you may be able to count and point out the conflicts.

What does this have to do with manual testing?

--------------------
- Joe
Visit AllThingsQuality.com to learn more about quality, testing, and QA!

I speak only for me. I do not speak for my employer, nor for anyone else.


Post Extras: Print Post   Remind Me!   Notify Moderator  
nawneet
Newbie


Reged: 03/31/08
Posts: 1
Re: Manual testing [Re: aadi]
      #471516 - 03/31/08 10:56 PM

Can anyone help with the flowchart (the procedures we follow) of manual testing.

Post Extras: Print Post   Remind Me!   Notify Moderator  
DSquared
Moderator


Reged: 04/02/03
Posts: 4546
Loc: Wisconsin, USA
Re: Manual testing [Re: nawneet]
      #471600 - 04/01/08 04:35 AM

Quote:

Can anyone help with the flowchart (the procedures we follow) of manual testing.




No one here can help you with the procedures you follow. Only someone at your company can help you with that.


Post Extras: Print Post   Remind Me!   Notify Moderator  
DSquared
Moderator


Reged: 04/02/03
Posts: 4546
Loc: Wisconsin, USA
Re: Manual testing [Re: Joe Strazzere]
      #471603 - 04/01/08 04:37 AM

Quote:

Once you know and understand all the requirements, then you may be able to count and point out the conflicts.

What does this have to do with manual testing?




My initial reaction was the same as yours, Joe. But then I started thinking and decided that since pointing out conflicts IS a form of testing, and it is not automated, about all that is left is manual.

I initially got locked into "manual testing" as testing the app, then remembered that there is a lot more to testing than just the app.


Post Extras: Print Post   Remind Me!   Notify Moderator  
tonybruce
Advanced Member


Reged: 06/22/07
Posts: 532
Re: Manual testing [Re: DSquared]
      #477343 - 04/22/08 03:28 AM

I would have thought that checking the requirements for conflicts would fall under Static Testing.

And as to the question, agree with the others, should be done after the requirements are reviewed, confirmed, and confirmed to be understood, and hopefully before any manual testing takes place.

If I was on a project where the requirements hadn't yet been checked for conflicts/reviewed and manual testing was being performed I'd be slightly worried.

--------------------
We live in the dumbest world on the planet and there's no colour the sky can't be at any given time. Remember that!
http://dancedwiththetester.blogspot.co.uk/
http://twitter.com/tonybruce77


Post Extras: Print Post   Remind Me!   Notify Moderator  
DSquared
Moderator


Reged: 04/02/03
Posts: 4546
Loc: Wisconsin, USA
Re: Manual testing [Re: tonybruce]
      #477358 - 04/22/08 04:45 AM

Quote:

I would have thought that checking the requirements for conflicts would fall under Static Testing.




Isn't static testing manual in nature? I don't know of a way to automate static testing.


Post Extras: Print Post   Remind Me!   Notify Moderator  
tonybruce
Advanced Member


Reged: 06/22/07
Posts: 532
Re: Manual testing [Re: DSquared]
      #477411 - 04/22/08 06:42 AM

Running the spell check!

--------------------
We live in the dumbest world on the planet and there's no colour the sky can't be at any given time. Remember that!
http://dancedwiththetester.blogspot.co.uk/
http://twitter.com/tonybruce77


Post Extras: Print Post   Remind Me!   Notify Moderator  
DSquared
Moderator


Reged: 04/02/03
Posts: 4546
Loc: Wisconsin, USA
Re: Manual testing [Re: tonybruce]
      #477433 - 04/22/08 07:21 AM

Ok, but does spell checking a requirements document really add that much value? It doesn't tell you when you have redundant requirements, conflicting requirements, incomplete requirements, etc. I know of no automation tools that will tell you those things.

Post Extras: Print Post   Remind Me!   Notify Moderator  
AOQA
Active Member


Reged: 04/12/07
Posts: 1044
Re: Manual testing [Re: DSquared]
      #477484 - 04/22/08 09:09 AM

You could create an automated framework around some elements of requirements review. For example, if you had a lot of requirements of a similar type (say, data entry field), a requirements-gathering framework could specify that all the requirements should have a field length, a data type, and a default. If those requirements were missing then the parent requirement would be incomplete, and identifying those missing requirements could be automated.

Post Extras: Print Post   Remind Me!   Notify Moderator  
tonybruce
Advanced Member


Reged: 06/22/07
Posts: 532
Re: Manual testing [Re: DSquared]
      #477559 - 04/22/08 12:02 PM

No, spell check was a joke but you're right, I don't know of an automated tool for this and I think if anybody ever managed to come up with something (apart from what Clint mentioned) it would require so much updating that there would be no value in it.

--------------------
We live in the dumbest world on the planet and there's no colour the sky can't be at any given time. Remember that!
http://dancedwiththetester.blogspot.co.uk/
http://twitter.com/tonybruce77


Post Extras: Print Post   Remind Me!   Notify Moderator  
thekid
Advanced Member


Reged: 01/07/07
Posts: 415
Loc: Castle Grayskull
Re: Manual testing [Re: tonybruce]
      #478790 - 04/26/08 06:13 PM

A flowchart is a flowchart and the only difference is the level of granularity you're aiming for. This is why the Visio Product Management team decided many years ago there was a need to include a standard set of symbols that are used for flowcharts. They can be a real pain in the rear to create for complex apps but they are worth their weight in gold from my experience and are vital for properly partitioning an app if you're test planning strategy includes equivalence class identification.

Identifying conflicting requirements is possible from the minute requirements are handed over to QA for review. Also keep in mind though there are reqs that you'll not see in a req doc because they are "implicit" reqs. The dev team must be crystal clear on how functionality should be implemented else , if conflicting reqs exist and questions are not asked, the dev team will make assumptions about desired functionality which in some cases results in incorrect assumptions and software that doesn't meet the needs of customers when builds are delivered to you.

--------------------
Reserve a few months every so often and preview retirement throughout your career. You won't regret that a 35 year career was reduced to 34 years to take vacations measured in months in order to remember what a stress and care-free life is all about.

Books and hard work will get you anywhere you want to go.


Post Extras: Print Post   Remind Me!   Notify Moderator  
JulianaSilvasan
Newbie


Reged: 11/24/11
Posts: 1
Re: Manual testing [Re: DSquared]
      #692101 - 11/28/11 02:45 AM

Quote:


Isn't static testing manual in nature? I don't know of a way to automate static testing.




I understand that automated testing for conflicting requirements is not common nor trivial, but I was wondering if static testing is indeed manual only.

I am new to the field and started learning for ISTQB and while doing that I've discovered that there are automated tools for static analysis of code, for example.
Would this make certain parts of static testing automated?
Or would you say that in order to be automated testing, it should first be dynamic?

Thanks,
.j


Post Extras: Print Post   Remind Me!   Notify Moderator  
Pages: 1



Extra information
0 registered and 2 anonymous users are browsing this forum.

Moderator:  blueinatl, swt88, AJ, Daniel_S 

Print Topic

Forum Permissions
      You cannot start new topics
      You cannot reply to topics
      HTML is disabled
      UBBCode is enabled

Rating:
Topic views: 12213

Rate this topic

Jump to

Contact Us | Privacy statement SQAForums

Powered by UBB.threads™ 6.5.5