|
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
What is the BEST WAY to write test cases?
Answer1:
1) List down usecases (taken from business cases) from function specs.
For each use case write a test case and categorize them into sanity tests, functionality, GUI, performance etc.
Then for each test case, write its workflow.
2) For a GUI application - make a list of all GUI controls. For each
control start writing test cases for testing of the control UI,
functionality (impact on the whole application), negative testing (for
incorrect inputs), performance etc.
Answer2:
1. Generate Sunny day scenarios based on use cases and/or requirements.
2. Generate Rainy Day (negative, boundary, etc.) tests that correspond
to the previously defined Sunny Day scenarios.
3. Based on past experience and a knowledge of the product, generate
tests for anything that might have been missed in steps one and two
above. These tests need not correspond to any documented requirements
or use cases. It's generally not possible to test every facet of the
design, but with a little work and forethought you can test the high
risk areas or high impact features.
What is the difference between build and release?
Builds and releases are similar, because both builds and releases are end products of software development processes. Builds and releases are similar, because both builds and releases help developers and QA teams to deliver reliable software.
A build is a version of a software; typically one that is still in testing. A version number is usually given to a released product, but sometimes a build number is used instead.
Difference number one: "Build" refers to software that is still in testing, but "release" refers to software that is usually no longer in testing.
Difference number two: "Builds" occur more frequently; "releases" occur less frequently.
Difference number three: "Versions" are based on "builds", and not vice versa. Builds (or a series of builds) are generated first, as often as one build per every morning (depending on the company), and then every release is based on a build (or several builds), i.e. the accumulated code of several builds.
How to test the memory leakeage mannually?
Answer1:
Here are tools to check this. Compuware DevPartner can help you test
your application for Memory leaks if the application is complex. Also
depending upon the OS on which you need to check for memory leaks you
need to select the tool.
Answer2:
Tools are more effective to do so. the
tools watch to see when memory is allocated and not freeed. You can
use various tools manually to see if the same happens. You just won't
be able to find the exact points where this happens.
In windows you would use task manager or process explorer (freeware
from Sysinternals) and switch to process view and watch memory used.
Record the baseline memory usage (BL) . Run an action once and record
the memory usage (BLU). Perform the same actions repeatedlty and then
if the memory usage has not returned to at least BLU, you have a
memory leak. The trick is to wait for the computer to clean up after
the transactions have finished. This should take a few seconds.
What is the difference between version and release?
Both version and release indicate particular points in the software development life cycle, or in the life cycle of a document. Both terms, version and release, are similar, i.e. pretty much the same thing, but there are minor differences between them.
Minor difference number 1: Version means a variation of an earlier or original type. For example, you might say, "I've downloaded the latest version of XYZ software from the Internet. The version number of this software is _____"
Minor difference number 2: Release is the act or instance of issuing something for publication, use, or distribution. Release means something thus released. For example, "Microsoft has just released their brand new gaming software known as _______"
How to write Test cases for Login screen?
the format for all test cases could be something like this
1. test cases for GUI
2. +ve test cases for login.
3. -ve test cases for login.
in the -ve scenario :- we should include boundary analysis to create test
cases ,Value Analysis. Equivalence Classes,Positive and Negative test cases)
plus cross-site scripting and SQL injection. SQL
injection is especially high-risk for login pages.
( Test case is Enter special char for username and it should displays a
message that username should have char a-z and 0-9 )
What is the checklist for credit card testing?
In credit card testing the following validations are considered
1)Testing the 4-DBC (Digit batch code) for its uniqueness (present on
right corner of credit card)
2)The message formats in which the data is sent
3)LUHN testing
4)Network response
5) Terminal validations
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
| 