|
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
When the build comes to the QA team, what are the parameters to be taken
for consideration to reject the build upfront without committing for
testing ?
Answer1:
Agree with R&D a set of tests that if one fails you can reject the build.
I usually have some build verification tests that just make sure the build is stable and the major functionality is working.
Then if one test fails you can reject the build.
Answer2:
The only way to legitimately reject a build is if the entrance
criteria have not been met. That means that the entrance criteria to
the test phase have been defined and agreed upon up front. This
should be standard for all builds for all products. Entrance
criteria could include:
- Turn-over documentation is complete
- All unit testing has been successfully completed and U/T cases are
documented in turn-over
- All expected software components have been turned-over (staged)
- All walkthroughs and inspections are complete
- Change requests have been updated to correct status
- Configuration Management and build information is provided, and
correct, in turn-over
The only way we could really reject a build without any testing,
would be a failure of the turn-over procedure. There may, but
shouldn't be, politics involved. The only way the test phase can
proceed is for the test team to have all components required to
perform successful testing. You will have to define entrance (and
exit) criteria for each phase of the SDLC. This is an effort to be
taken together by the whole development team. Developments entrance
criteria would include signed requirements, HLD doc, etc. Having
this criteria pre-established sets everyone up for success
Answer3:
The primary reason to reject a build is that it is untestable, or if
the testing would be considered invalid.
For example, suppose someone gave you a "bad build" in which several of
the wrong files had been loaded. Once you know it contains the wrong
versions, most groups think there is no point continuing testing of
that build.
Every reason for rejecting a build beyond this is reached by agreement.
For example, if you set a build verification test and the program fails
it, the agreement in your company might be to reject the program from
testing. Some BVTs are designed to include relatively few tests, and
those of core functionality. Failure of any of these tests might
reflect fundamental instability. However, several test groups include a
lot of additional tests, and failure of these might not be grounds for
rejecting a build.
In some companies, there are firm entry criteria to testing. Many
companies pay lipservice to entry criteria but start testing the code
whether the entry criteria are met or not. Neither of these is right or
wrong--it's the culture of the company. Be sure of your corporate
culture before rejecting a build.
Answer4:
Generally a company would have set some sort of minimum goals/criteria that a build needs to satisfy - if it satisfies this - it can be accepted else it has to be rejected
For eg.
Nil - high priority bugs
2 - Medium Priority bugs
Sanity test or Minimum acceptance and Basic acceptance should pass
The reasons for the new build - say a change to a specific case - this should pass
Not able to proceed - non - testability or even some more which is in relation to the new build or the product
If the above criterias don't pass then the build could be rejected.
What is software testing?
Software testing is more than just error detection;
Testing software is operating the software under controlled conditions, to (1) verify that it behaves “as specified”; (2) to detect errors, and (3) to validate that what has been specified is what the user actually wanted.
Verification is the checking or testing of items, including software, for conformance and consistency by evaluating the results against pre-specified requirements. [Verification: Are we building the system right?]
Error Detection: Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldn’t or things don’t happen when they should.
Validation looks at the system correctness – i.e. is the process of checking that what has been specified is what the user actually wanted. [Validation: Are we building the right system?]
In other words, validation checks to see if we are building what the customer wants/needs, and verification checks to see if we are building that system correctly. Both verification and validation are necessary, but different components of any testing activity.
The definition of testing according to the ANSI/IEEE 1059 standard is that testing is the process of analysing a software item to detect the differences between existing and required conditions (that is defects/errors/bugs) and to evaluate the features of the software item.
Remember: The purpose of testing is verification, validation and error detection in order to find problems – and the purpose of finding those problems is to get them fixed.
What is the testing lifecycle?
There is no standard, but it consists of:
Test Planning (Test Strategy, Test Plan(s), Test Bed Creation)
Test Development (Test Procedures, Test Scenarios, Test Cases)
Test Execution
Result Analysis (compare Expected to Actual results)
Defect Tracking
Reporting
How to validate data?
I assume that you are doing ETL (extract, transform,
load) and cleaning. If my assumetion is correct then
1. you are builing data warehouse/ data minning
2. you ask right question to wrong place
What is quality?
Quality software is software that is reasonably bug-free, delivered on time and within budget, meets requirements and expectations and is maintainable. However, quality is a subjective term. Quality depends on who the customer is and their overall influence in the scheme of things. Customers of a software development project include end-users, customer acceptance test engineers, testers, customer contract officers, customer management, the development organization's management, test engineers, testers, salespeople, software engineers, stockholders and accountants. Each type of customer will have his or her own slant on quality. The accounting department might define quality in terms of profits, while an end-user might define quality as user friendly and bug free.
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
| 