What is smoke testing and when it will be done?
Answers were Sorted based on User's Feedback
Answer / swathi
Smoke Testing: Executing the application to check whether it
is free from errors or not. It should be done as soon as we
receive the Build from the developer.
| Is This Answer Correct ? | 13 Yes | 3 No |
Answer / sethupathy
Smoke Testing: Testing the application to know whether the
application is eligible to test is called smoke testing. It
means there should some piece of code should be working for
the testers to test and proceed further. This testing is
done many times to check does the application meet
acceptance criteria to start testing.
Ex: There might be a case "dll not found error" seen when
you launch the application after installing. What testing
can you do when you cannot launch the application?
| Is This Answer Correct ? | 8 Yes | 0 No |
Answer / saravana
Its an early stage of testing process. We carry out smoke
testing for checking the stability of the build. Whether
the build is ready for testing or not.If smoke testing is
failed then the build is rejected.
| Is This Answer Correct ? | 8 Yes | 1 No |
Difference between System Testing and System Intergration Testing(SIT) with Example
what is the Exact difference between Sanity and Smoke testings
how often do u recieve bulid in ur company?
I have one year of experience in IT as tester.Do i know any openings,if u heard?
I have password field in my application.while entering data into pwd field the characters are not encrypted will it come under gui testing or unit testing? is gui testing checked by typing or entering data into fields?
What are the bugs we cannot find in black box?
For a functionality we have 20 test cases, among 20 testcases 15 of them are Passed and 5 Failed. How will you report to your Manager ? Does the functionality passed or failed or partial passed/failed ??
4. A software error can be described as: a. A description of the relationship between two or more variables or set members in which the value of one does not influence the values of others. b. Any ill-advised, substandard, or temporary fix applied to an urgent problem in the (often misguided) belief that doing so will keep a project moving forward. c. The process in which developers determine the root cause of a bug and identify possible fixes. d. A mismatch between the program and its specification. 5. Select a reason that does not agree with the fact that complete testing is impossible: a. The domain of possible inputs is too large to test. b. Limited financial resources. c. There are too many possible paths through the program to test. d. The user interface issues (and thus the design issues) are too complex to completely test.
You reported a Bug.The developers are saying that it's not a Bug even though it is..How you are going to prove that it's a Bug?
What is meant by Entry and Exit points in Testing? Raam - ramumcato@yahoo.com
what is deffered defect?
On what basis is the Acceptance plan prepared?