Task-4
1.Describe differences between
a. Smoke and sanity Testing
| Comparison Basis | Smoke Testing | Sanity Testing |
| Test coverage | It is a broad approach to testing where all parts of the application are tested. | It is a narrow approach to testing where specific parts of the application are tested. |
| Measures | It measures the stability of the system by performing rigorous testing. | It measures the rationality of the system by performing rigorous testing. |
| Technique | Smoke testing can be either manual or automated. | Sanity testing can be done without test cases or scripts. |
| Executed by | It is performed by both testers and developers. | It is performed by only testers. |
| Purpose | Testing is done without getting into deep but whenever needed tester has to go into deep. | Sanity testing does not need to go into deep of the application. |
| Performed at | Smoke testing is the first testing performed on the initial build. | Sanity testing is performed when the build is comparatively stable. |
| Documentation | Smoke testing is documented. | Sanity testing is not documented. |
| Used to | It is used to test End to End function of the application. | It is used to test only modified or defect fixed functions. |
| Subset | It is considered as a subset of acceptance testing. | It is considered as a subset of regression testing. |
b.validation and verification
| Verification | Validation |
| We check whether we are developing the right product or not. | We check whether the developed product is right. |
| Verification is also known as static testing. | Validation is also known as dynamic testing. |
| Verification includes different methods like Inspections, Reviews, and Walkthroughs. | Validation includes testing like functional testing, system testing, integration, and User acceptance testing. |
| It is a process of checking the work-products (not the final product) of a development cycle to decide whether the product meets the specified requirements. | It is a process of checking the software during or at the end of the development cycle to decide whether the software follow the specified business requirements. |
| Quality assurance comes under verification testing. | Quality control comes under validation testing. |
| The execution of code does not happen in the verification testing. | In validation testing, the execution of code happens. |
| In verification testing, we can find the bugs early in the development phase of the product. | In the validation testing, we can find those bugs, which are not caught in the verification process. |
| Verification testing is executed by the Quality assurance team to make sure that the product is developed according to customers' requirements. | Validation testing is executed by the testing team to test the application. |
| Verification is done before the validation testing. | After verification testing, validation testing takes place. |
| In this type of testing, we can verify that the inputs follow the outputs or not. | In this type of testing, we can validate that the user accepts the product or not. |
explain about the agile methodology.
Agile methodology is a project management framework that breaks projects down into several dynamic phases, commonly known as sprints. Unlike traditional linear approaches, Agile is iterative. After each sprint, teams reflect and assess if there are areas for improvement, allowing them to adjust their strategy for the next sprint. Here are some key points about Agile:
Agile Manifesto: The Agile Manifesto, published in 2001 by 17 software developers, outlines four values and 12
principles for Agile software development. It emphasizes flexibility, collaboration, and responsiveness to change.Four Pillars of Agile: Individuals over processes and tools: Agile prioritizes team collaboration and teamwork over rigid processes. Working software over comprehensive documentation: The focus is on delivering functional software rather than extensive documentation.
Customer collaboration over contract negotiation: Customer input guides software development.
Responding to change over following a plan: Agile allows teams to adapt quickly to changing requirements.
Benefits of Agile: Flexibility: Agile allows teams to shift strategies and workflows without derailing the entire project. Continuous improvement: Regular reflection and adjustment lead to better outcomes. Applicability beyond software: Agile works well for various types of teams, not just software development.
3.Explain Epic and User stories?
Epics is a hierarchy of work, composed of smaller to-dos and user stories, that your team completes over multiple sprints. Within the Agile paradigm, epics are crucial because they give teams a useful, shared vocabulary and method to utilize when organizing their work.
The tasks are completed in short bursts of time called sprints.
The goals within an epic are called stories and within the stories are tasks called objectives.
The epic hierarchy is a way of dividing large goals into smaller units to allow for rapid iterative revisions.
The development backlog can have many future epics identified and prioritized and, just in time, we break them down only when we’re nearing the time that we’re getting ready to deliver them.
Agile epics break your stories down into more manageable chunks, collecting those tasks and splitting the workload into a more realistic flow.
User story
User stories give the team important context and associate tasks with the value those tasks bring. During a sprint or iteration planning meeting, the team decides what stories they’ll tackle during that sprint. These are a way to communicate and manage user requirements.