|
Software QA/Testing Technical FAQs
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
500 Internal Server Error problem while doing load testing using Microsoft Web Application Stress Tool
When doing Load testing using WAS (Microsoft Web Application Stress
Tool), get " 500 Internal Server Error" problem for most
of the "POST" querries. The Log file it showed the following
data:
"GET /imse/Global/images/Default/arrow.gif 500"
"GET /imse/client/Template/images/Default/arrow.gif 500"
"GET /imse/client/Template/images/Default/Plus1.gif 500"
What could be the reason for this?
The problem is because the response will have not come. The session will
have timed out. This will be the application will have taken more memory.
This might be because of multiple threads running with each thread taking
much CPU time. Please check the Server of the system where the build is
deployed for Heap Dump. The Garbage collector will have created Java Heap
and Core dumps in the Application folder.
Try increasing the number of DB Connections in the server. This might solve
the Problem. Also increase the Final Heap size also. This might solve the
problems.
How do you check the security of an application?
To check the security of an application, one can use security/penetration testing. Security/penetration testing is testing how well a system is protected against unauthorized internal, or external access, or willful damage. This type of testing usually requires sophisticated testing techniques.
How do I write a Test Case?
Read the following:
What Is a Good Test Case?
Cem Kaner
How to Write Better Test Cases
Dianne Runnels
Reducing Test Case Documentation Time
Ranjit Shewale
Testing in the Dark: A pragmatic approach to overcoming undocumented
requirements
By Johanna Rothman/Brian Lawrence
Session-Based Test Management: A strategy for structuring exploratory testing
By Jonathan Bach
Adventures in Session-Based Testing
By James Lyndsay
An Introduction to Scenario Testing
By Cem Kaner
How to estimate product test hours for new releases?
Answer1:
Your main task is to convince your company of the
- value of structured testing and the benefits it brings to the end product
- the risks of not testing properly (high maintenance, lots of bugs found in
production (and these generally found by your customers!), loss of market
reputation ("another crap product from xyz company).
Another approach might be to consider starting your test processes earlier
(i am guessing from your message that you are following some kind of
waterfall method) - its a sort of 'design a little, build a little, test a
little, design a little ...' approach.
Answer2:
Tell the folks making decisions to read user feedback. No time for
testing = angry users who want their money back or worse angry clients
who suddenly hire a team of lawyers.
Warned all the
stakeholders early on and then sent user feedback emails up the chain.
Users can be brutal and they tell the truth! Comments like YOU SUCK!!
It may also convince them to get more support people instead of
increasing testing.
Answer3:
The ratios:
3/1 Developers to QA (industry)
3/2 Developers to QA (Microsoft)
There is also a really good article called "A Better Bug Trap"
published by The Economist in 2004, which is pretty telling: according
to NIST 80% of a
software project belongs to testing and debugging.
There is also the classic book called "Mythical Man Month". There are a
couple of pertinent passages there:
1) Back when the book was written, the percentage quoted by NIST was
50%, which means that software development has become less efficient
over the last 20 years or so.
2) There is a 30% that a change in any line of code will break
something down stream.
3) There is another article published by McKinsey Quarterly called "What
high tech can learn from slow-growth industries".
When testing the password field, what is your focus?
When testing the password field, one needs to focus on encryption; one needs to verify that the passwords are encrypted.
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
| 