Give me sample test cases for smoke testing.
So talking about smoke testing in the context of software applications, the purpose of such a test process is to ensure whether the application already under test, is efficient enough to pass through further levels of testing. Test cases are prepared to carry out the preliminary litmus tests on an application before passing it on for further testing.
Test cases should be written by a team member who understands the function or technology being tested, and each test case should be submitted for peer review. Organizations take a variety of approaches to documenting test cases; these range from developing detailed, recipe-like steps to writing general descriptions.
There are many types of test cases such as functional, negative, error, logical test cases, physical test cases, UI test cases, etc. Furthermore, test cases are written to keep track of the testing coverage of a software. Generally, there are no formal templates that can be used during test case writing.
No. Not at all. Regression test is another type of retesting only hence we execute the all ready written test cases. Now comes the question what’s the difference between retesting and regression? well, every time there is a code change which might.
Unit testing is a form of white-box testing, in which test cases are based on an internal structure. The tester chooses inputs to explore particular paths and determines the appropriate output.
The terminologies such as Smoke Test or Build Verification Test or Basic Acceptance Test or Sanity Test are interchangeably used, however, each one of them is used under a slightly different scenario. Sanity test is usually unscripted, helps to identify the dependent missing functionalities. It is used to determine if the section of the application is still working after a minor change.
One of the complexities that arise in a microservices architecture based application is about testing different micro-services. For each micro-service, one can write unit test cases by mocking.