Ten things to avoid in a website

Ten things to avoid in a website

1. Frames
2. Over-use of "leading-edge" technology
3. Scrolling text, marquees, and animations
4. Complex URLs
5. Orphan pages
6. Long scrolling pages
7. No navigation support
8. Non-standard link colors
9. Outdated information
10. Long download times

Why do bugs occur ?

Question:- Why do bugs occur ?

Answer:- There are so many reasons for bugs to occur:-
1) Miscommunication or no communication
2) Unclear requirements
3) Time lines
4) Human errors
5) Technical reasons
6) Frequent changes in requirements
and so on...

Test Report

Dear friends,

In our company our team members follow the procedure below,
our Test report contains,
1.Revision History
2.Test case Index
3.Version Details
4.Test cases.
5.Defect/Error Report


What is the document procedure u all are using in ur company?
it'd be fine if we can share our ideas , for a beter Test Report .

Re: Difference between functional and technical tester?

On Mon, Jul 21, 2008 at 2:06 AM, preethi menon wrote:

Hi brijesh,

what is the difference between functional tester and technical tester?

regards

Preethi

Hi,

Break the word "technical tester", into "technical" and "tester". What do you thing if we say functional tester, it means it is related to software functionality. No, functional testing is a general term, and as we are talking about software in our discussion, so, it is understood that we are saying software functional testing.
In the same way, anything related to technology is technical, it may be related to software technology, electronic technology or anyone. A software tester is also a technical tester. There is no such difference between functional tester and technical tester, a functional tester is also a technical tester.
Correct me, if I am wrong. I may also wrong.

If developer do not accepts a bug; then what to do?

Question:- If developer do not accepts the bug; then what to do?

Answer:- Hi, many times this situation occurs, when a tester find the bug and report it to developers to fix. But still developers say no to fif the bug. The reason may not be that developers don't want to fix it. Reason may be:-

1) A related bug is already posted, so developer knows that fixing that bug will fix it automatically.
2) Developer is unable to reproduce the bug.
3) Developer is unable to understand the bug.
4) This is not a bug but functionality.
5) May be functionality has been changed.

In any case,
1)tester should communicate with developer and should ask for problem he is facing in reproducing the bug.
2)Ask him for additional help he wants.
3)Try to elaborate the bug report more every time you report the bug.

Re: Manual Software Testing

On Wed, Jul 16, 2008 at 12:31 AM, Anitha Saraswathi loganathan wrote:

Hi Brijesh,

my name is Anitha,

Regards to u.......

u r doing a great job..........

thank u so much for sharing ur knowledge & helping us .

what kind of questions will be asked in practical tests for s/w testing?

cud u reply soon pl..............

--
Thank you

BEST REGARDS.
AnithaLoganathan

Hi Anitha Saraswathi loganathan,

Nice to see your mail and for such a loving words. Actually questions depend on company work. In which technology company is working and what they are expecting from the candidate. You have not told me anything about the experience you have in testing. But for freshers the most important is logical thinking and basic knowledge of testing. Questions related to test cases and test plan are the most common questions to be asked by interviewers.

What about this Gmail Bug?

What about this Gmail Bug?

Is it interesting? I post it here, just to show my friends that no software is bug free, whether it is how much tested. So, keep testing and you will get the bug. Don't be satisfied that you have done enough testing, play with code, and you will get the loop hole.

Enjoy :)

Pitfalls to manual software testing

Pitfalls to manual software testing, including:

1. Manual testing is slow and costly.
2. Manual tests do not scale well.
3. Manual testing is not consistent or repeatable.
4. Lack of training.
5. Testing is difficult to manage.
6. Time consuming.
   

Re: bugs..its very urgent

On Thu, Jul 10, 2008 at 10:49 PM, keerthika reddy wrote:

Hi Brijesh,

This is Keerthika. Your blog is awesome n u r doin a wonderful job dude!!!

Brijesh i hav sum queries reagrdin bugs

what could be the (realtime)bugs you come across in job portal and health care projects in terms of
1. high severity n low priority
2. high severity n high priority
3. low severity n low priority
4. low severity n low priority?
pls its very urgent

thanks in advance n lukin forward for ur reply

once again ur blog explores so much information abt testing n its quite useful 2.

Hi Keerthika,

Nice to see your mail. Thanks for such loving words. As per your question, I will tell you something first.

You should understand "Severity and Priority" first. Read about these terms, try to understand them. You can search and read about them on this blog itself. Why I am suggesting it to you? Because, not me but anyone can't answer your such type of questions. You have to find the solutions yourself, and you will, I am sure about it. I can give you gun, but you have shot it your self in battle.

Give me the description of the bug, you face during testing, I will tell you the severity of that bug to you. Let the priority to decide by your test manager, why to take tensions? :)

You may have live chat with me, If I am online and have time.

Re: QTP (Quick Test Pro)

On Mon, Jul 7, 2008 at 6:21 PM, Prameela Duddala wrote:

Hi: In short time how did you become Sr tester??

I notice that u have lot of knowledge about the testing. how did you learn in a short period of time? let me know the secrete I too want to learn. u answer almost any question any body will ask you. really I am yoou fan. Thanks & Regards, Prameela

Hi prameela,

Thanks for your compliments. I really feel happy when I make someone happy. As per secret, there is nothing like that. I know only one thing,

"Knowledge improves with sharing. Share to learn."

So, I always share my experiences with the world. You may also try it.

Re:

Hi bhagirath nagaraju,

Testing is not a magic stick, that you will roll and get the bugs in few seconds. It depends on business and application. It depends on risk, and more it depends on tester, who have to test the application. Still I will suggest you to to make a "Dry Run" of application, I am not sure whether dry run of your application can be completed within time period or not. But I will not suggest to dispatch a software without at least "Dry Run".

On Mon, Jul 7, 2008 at 1:38 AM, bhagirath nagaraju <bhagirath.61@gmail.com> wrote:

sir,

If we have thousands lines of coding and we have to dispatch the software next day morning then which type of testing we needed to do?

Interview Question

Interview Question:- We have to design test Cases for an Application having almost same functionality for all users. But application also consist other functionality issues which is assign to only specific Users who have more rights in the Application like a Senior User can Approve and Modify his/her Junior task. So how I should prepare Test Cases w.r.t User (Senior & Junior, Admin) or w.r.t. functionality?

Answer:- I will suggest to test the functionality at highest level.

Then do security testing for junior levels, what they allowed to do, what not.

Because why to test same functionality again and again for all levels users, when we can test it at top level.

As said in question "Application also consist other functionality issues which is assign to only specific Users",

Actually this is not the functionality but security of the application as per my view.

If any reader suggest some good solution, his/her comments are welcomed.