Q-1-> Describe the difference in between:
1) Smoke and sanity testing
Answer
Smoke Testing
- It is board approach where all parts of application are tested.
- It is tested by either manual or automation testing.
- It is performed by both developer and tester.
- Smoke testing is the first test performed on the initial build.
- It is considered as subset of acceptance testing.
- Smoke testing is documented.
- It is used in end to end function of application.
Sanity Testing
- it is narrow approach where some specific parts of application are tested.
- It is test can be done without scripts.
- It is performed by testers.
- Sanity testing is performed when the application is comparatively stable.
- It is considered as subset of regression testing.
- Sanity testing is not documented.
- It is used to test the modified and bug fixed function.
==============================================
2) Verification and Validation
Answer
Verification
- We check whether we are developing the right product or not.
- Verification is also known as static testing.
- Verification process includes like inspections, reviews nd walkthroughs
- Quality Assurance is comes under verification.
- Code of execution doesnt happen in verification.
- Verification is performed by quality assurance team whether the product is developed according to customer's requirements.
- It is performed before the validation process.
- In verification, we can find the bugs early in the development phase.
Validation
- We check whether the product meets the requirements or not.
- Validation is also as dynamic testing.
- Validation process includes unit testing, system testing, user acceptance etc.
- Quality Control is comes under validation.
- Code of execution is happens in validation.
- Verification is performed by tester team whether the product is meets the BA's requirements.
- It is done after the verification process.
- We can find the bugs where they are not found in verification process.
===============================================
Q-2-> Explain about agile methodology.
Answer
An agile methodology is an iterative approach to software development. Each iteration of agile methodology takes a short time interval of 1 to 4 weeks. The agile development process is aligned to deliver the changing business requirement. It distributes the software with faster and fewer changes.
The single-phase software development takes 6 to 18 months. In single-phase development, all the requirement gathering and risks management factors are predicted initially.The agile software development process frequently takes the feedback of workable product. The workable product is delivered within 1 to 4 weeks of iteration.
A small group of peoples from agile developing the software is called agile squad.
There are five agile ceremonies conducted in agile by scrum master.
- Sprint Grooming
- Sprint Planning
- Daily Standup
- Sprint Review
- Sprint Retrospective
=================================================
Q-3-> Explain about epic and user story?
Answer
Epic
- It contains the large bodies of requirement, analysis, contents in few lines.
- A single epic can broke into multiple stories.
- Epic is a headline of automation scripts.
- It is created by business analyst for developers and testers.
- Example : Create a shopping website which is user-friendly and have multiple advance options in it.
User Story
- It Contains small amount of content to develop and test in short period.
- A multiple user stories becomes a single epic.
- User story is sub-topic of Epic.
- It is created by also business analyst for short term.
- Example : Add voice command to the shopping website for easy access.
Top comments (0)