When the developer do not accepts it is a bug then what to do?

what is blackbox testing and white box testing?

Hi friend....

According to my view...

black box:
It tests only the external features of the application.. There is a form named A and the buttons such as radiobutton should be placed on the right of the form then the button should be placed in the screen right side.. we only check the button is placed right

white box:
It check the internal function of the application.. such as in the form if there is a link and by clicking the link the navigation should be done to the form named B. Then we should whether the link gets navigated

If the developer does not accept the bug: This is due to the developer did not understand the severity of the bug.. Tell the route cause of the bug and make make him to analyze. or else send the report to the test manager..

Friends correct me if i am wrong...

Thanks
Deepasree

Hi,

If there is a conflict between priortised BRS and testing scenario then developer might neglect it to be a bug.

Cheers,
Sridevichitthu

hi...
when ever the build#1 is realsed we can do the re-testing, if there is any bugs then by using the testDirector/Q.C the test engg take a snape shot and it send to developer, it is bug no problem, if the developer not agree with that then we inform to the TL ot PM,

1)Tester should communicate with developer and should ask for problem he is facing in reproducing the bug.
2)Try to elaborate the bug report more every time you report the bug.


Software Testing Expertise: If developer do not accepts a bug; then what to do?

__________________
Brijesh Jain
brijesh.tester@yahoo.co.in
http://softwaretestingexpertise.blogspot.com

Hi everyone... I would suggest that at the time of reporting an issue always give a detailed steps to reproduce the bug and it is always preferable to attach a screen shot as it will make more clearer to the developer. Simple definitions: black box testing -testing of a function without knowing internal structure of the program.that is you do not need to know anything about coding. White box testing -testing of a function with knowing internal structure of the program.you should be aware of coding, testing the coding part itself is called as white box testing. Hope that my answer is helpful to you all...suggestions and corrections are always welcome..

Black box testing is not releated to backend structure, & not also it inculde software languages. It is related to functional testing, inpute should be entered correct & output should be display properly. It is related to all the functionality of models. Tester should have the domain knowledge & need SRS document.

White box testing is related to testing of code so tester should knowledge of coding, backend structure, software languages.

Black box testing - not based on any internal design or code. Tests are based on requirements and functionality.
White box testing - based on knowledge of the internal logic of the application's code.Tests are based on coverage of code statements,branches,paths,conditions.

Its hard to convince the developer that there is a bug in the application developed by him/her, for that you need to

1. Reporduce that in the earlier versions
2. Write the steps in detail, from the scratch(even if the developer is aware) of the steps
3. Give as much as info you can, attach the relevant materila , screenshots etc.
4. Try to say on which database/version etc is the issue happening.

Blackbox Testing:Black box testing takes an external perspective of the test object to derive test cases. These tests can be functional or non-functional, though usually functional. The test designer selects valid and invalid input and determines the correct output. There is no knowledge of the test object's internal structure.

White Box Testing;White box testing (a.k.a. clear box testing, glass box testing or structural testing) uses an internal perspective of the system to design test cases based on internal structure. It requires programming skills to identify all paths through the software. The tester chooses test case inputs to exercise paths through the code and determines the appropriate outputs. In electrical hardware testing, every node in a circuit may be probed and measured; an example is in-circuit testing (ICT).

hi,

thats a good question, its hard to convice the developer when reporting the bug, but when we take necessary actions then it would be easy

1. When raising the bug, try to write all the steps in "Steops to Reproduce" section, do not miss even a single step
2. Compare the last version and latest version, where you found the issue
3. Try to attch all the screenshots, documents, files etc

Blackbox Testing:Black box testing takes an external perspective of the test object to derive test cases. These tests can be functional or non-functional, though usually functional. The test designer selects valid and invalid input and determines the correct output. There is no knowledge of the test object's internal structure. This method os testing is applicable to all levels of software testing.

White box testing:White box testing (a.k.a. clear box testing, glass box testing or structural testing) uses an internal perspective of the system to design test cases based on internal structure. It requires programming skills to identify all paths through the software. The tester chooses test case inputs to exercise paths through the code and determines the appropriate outputs.While white box testing is applicable at the unit, integration and system levels of the software testing process, it is typically applied to the unit