what is non incremental integration testing?
Answers were Sorted based on User's Feedback
Answer / laxman
We should know the parent / child relationship between the modules means which module is the parent / child of which module is called as incremental integration testing.
But if we do not know the parent / child relationship between modules then we should go for Non-Incremental Integration Testing..
Is This Answer Correct ? | 15 Yes | 2 No |
Answer / vidya
non incremental integration testing is combining all the modules at a shot and testing the data flow between these modules.It will be difficult to identify which is the parent module and which is the child module.
Is This Answer Correct ? | 13 Yes | 1 No |
-Non increamental integration testing is otherwise called a
as 'Bing-Bang' approach.
-Bing-bang approach is testing at a go by combining all the
modules at a time.
Is This Answer Correct ? | 19 Yes | 11 No |
Answer / prajwal n s
Combine all the modules together at a time at a short and test the data flow between them is called as Non Incremental Integration testing.
When it is difficult to identify which is the parent and which is the child module we go for NIIT(Non Incremental Integration testing).
When the data is complex we go for NIIT.
There are drawbacks in NIIT such as we cannot find the root cause of the defect and there are some chances we might miss the data flow between 2 modules.
Is This Answer Correct ? | 3 Yes | 1 No |
Answer / nikhil gulhane
The non incremental approach is also known as “Big-Bang” testing. This approach is very unfashionable due to the level of risk that one takes in hoping that the system will perform as expected.
Is This Answer Correct ? | 2 Yes | 1 No |
what are the differences between stub abd the driver ?
Hierarchy of Regression Testing?
what is the roles and responsibilities of qa manager
Which metric is used for extent of testing? a.)User Participation b.)Acceptance criteria tested c.)Test Cost d.)Test Automation
Difference between Agile process and V Model
What is your daily process? and roles and responsibility? please answer this question this is very imp question. I am putting 2+years of experience.
if u find bug is duplicated is it needed to again log it .how do u find bug is duplicated using test director as a tool
can anyone give me example of the following:- low severity & high priority medium severity & medium priority high severity & low priority
What are the advantages of black box testing?
email id test@test.com is it valid email id or not why is the email id is not valid?
can i manage putting fake experience in manual testing what they will do if am caught
Suppose wihile we are doing testing..A bug is reproduced what will be the necessary action taken by the tester?