Software Testing Tutorial #9 - V Model in Software Engineering

Поділитися
Вставка
  • Опубліковано 4 сер 2024
  • Get all my courses for USD 5.99/Month - bit.ly/all-courses-subscription
    In this Software Testing Tutorial, we will learn what is the V model is software engineering. V model is an improvement over the issues that we had in waterfall development approach.
    In V Shaped model the testing team gets involved in every phase of software development lifecycle and addressed the major drawback of Waterfall model where testing phase was very late in software development life cycle.
    🔸FREE Training's at training.rcvacademy.com 🔔SUBSCRIBE to CHANNEL: bit.ly/2YGU6JM
    Help me in spreading the knowledge, please hit LIKE, SHARE, and SUBSCRIBE for the latest tutorials. More tutorial playlists below:
    ✅ ALL PLAYLISTS (Software Testing Mentor)🔸 / softwaretestingmentor
    ✅ ALL PLAYLISTS (RCV Academy)🔸 / @rcvacademy
    ✅ JIRA BEGINNER TUTORIAL🔸 bit.ly/jira-beginner-tutorial
    ✅ JIRA WORKFLOW TUTORIAL🔸 bit.ly/2EzKOEB
    ✅ JIRA ADMINISTRATION TUTORIAL🔸 bit.ly/36MPPFR
    ✅ JIRA TUTORIAL INTERMEDIATE🔸 bit.ly/Atlassian-JIRA-tutorials
    ✅ JIRA TUTORIALS🔸 bit.ly/jira-tutorials
    ✅ ZEPHYR TUTORIAL🔸 bit.ly/zephyr-for-jira-tutorials
    ✅ SOAPUI TUTORIAL🔸 bit.ly/Sopui-tutorial
    ✅ JSONPath TUTORIAL🔸 bit.ly/2sIZIFG
    ✅ POSTMAN TUTORIAL🔸 bit.ly/2PBbhI7
    ✅ ISTQB AGILE TESTER CERTIFICATION TUTORIAL🔸 bit.ly/istqb-agile-tester-cert...
    ✅ ISTQB FOUNDATION LEVEL CERTIFICATION TUTORIAL🔸 bit.ly/istqb-foundation-level-...
    ✅ CUCUMBER SELENIUM TUTORIAL🔸 bit.ly/cucumber-selenium-tutorial
    ✅ TESTRAIL TUTORIAL🔸 bit.ly/testrail-tutorial
    ✅ AGILE TUTORIALS🔸 bit.ly/agile-tutorials
    ✅ PYTHON TUTORIALS🔸 bit.ly/python-programming-tuto...
    ✅ PYTHON BEHAVE TUTORIALS🔸 bit.ly/python-behave-tutorial
    ✅ PRACTITEST TUTORIAL🔸 bit.ly/practitest-tutorial
    ✅ JAVA TUTORIAL🔸 bit.ly/2F1iL1B
    ✅ ZEPHYR TUTORIAL🔸 bit.ly/zephyr-for-jira-tutorials
    🔶 ENROL IN MANY FREE TRAININGS ON RCV ACADEMY PORTAL 🔶
    training.rcvacademy.com/
    🔶 FOLLOW US ON TWITTER 🔶
    / rcvacademy
    / swtmentor
    / mrmverma
    🔶 LIKE US ON FACEBOOK 🔶
    / softwaretestingmentor
    / rcvacademy47
    🔶 OUR TUTORIAL WEBSITES 🔶
    www.softwaretestingmentor.com
    www.rcvacademy.com
    🔶 GET MY TRAININGS ON UDEMY 🔶
    www.udemy.com/user/manish68/
    #SoftwareTestingTraining #SoftwareTestingTutorial #SoftwareTestingBootcamp #SoftwareTesting #QA #QATraining #QATutorials #RcvAcademy #SoftwareTestingMentor

КОМЕНТАРІ • 26

  • @manoj_mafiosi
    @manoj_mafiosi 11 місяців тому +16

    ** Software Testing Tutorial #9 - V Model in Software Engineering - Notes**
    **V Model Overview:**
    - The V Model's name derives from its shape resembling a "V."
    - Unlike the linear progression of the waterfall model, the V Model involves incremental phases with corresponding testing stages.
    - Addresses the issue of delayed feedback and testing in the waterfall approach.
    **Phases of the V Model:**
    1. **Requirements Gathering:**
    - Begins with requirements gathering similar to SDLC and waterfall.
    - Key shift: Testing involvement starts in this phase.
    - Testing team creates user acceptance test cases based on high-level requirements.
    - Early involvement identifies gaps and potential issues from the outset.
    2. **System Analysis and Design:**
    - Focuses on software's interaction with underlying systems.
    - Testers draft system test cases targeting end-to-end testing.
    - Integration with third-party systems or existing components is emphasized.
    3. **Global Design and Detailed Design:**
    - Global design outlines software architecture and external system interfaces.
    - Testing team formulates integration test cases.
    - Detailed design deals with specific modules, developers construct smaller modules, and testers write unit tests.
    4. **Coding and Unit Testing:**
    - Developers write actual code for modular components.
    - Unit testing executed, often by developers, and might involve white box testers for closer code examination.
    5. **Integration Testing:**
    - Scrutinizes integrated modules' interaction and compatibility.
    6. **System Testing:**
    - Comprehensive phase testing software's entirety under various conditions.
    7. **User Acceptance Testing:**
    - Stakeholders from business or customer side test software against specific needs.
    - User acceptance test cases executed based on requirements.
    **Advantages of the V Model:**
    - Testing team involvement across all development stages.
    - Early participation enables early defect detection, enhancing software quality.
    - Ensures feedback loops at every phase, unlike the concentrated testing involvement in the waterfall model.
    **Conclusion:**
    - The V Model enhances software development by incorporating testing from the beginning.
    - Iterative approach alleviates risks of late-stage defect discovery.
    - Collaborative integration of development and testing efforts fosters a reliable software development life cycle.

  • @paulaartigas3944
    @paulaartigas3944 2 роки тому +5

    Thank you so much for this video and for using examples! Very helpful!

  • @feeldulfo9387
    @feeldulfo9387 Рік тому +1

    Thanks for sharing your knowledge!!!

  • @user-fu6nc9qs7o
    @user-fu6nc9qs7o 10 місяців тому

    Thankyou. Very helpful

  • @elnino61
    @elnino61 2 роки тому

    Thanks a lot.

  • @gyanbaimishra9466
    @gyanbaimishra9466 Рік тому +1

    Thank you sir

  • @micho-ub5hx
    @micho-ub5hx 2 роки тому +3

    Por fin entiendo de que se trata esto, la parte importante con el testing es que despues que se alcanza la implementación es que inicia la ejecución de las pruebas. Muchas gracias, muy duro usted.

    • @nikolavukovic5678
      @nikolavukovic5678 2 роки тому

      si y el hombre lo escplica como en las escuela.. que testing es parte grande i se debe aplicar temrpano en el proceso.. agradesco

  • @sebnembayezit969
    @sebnembayezit969 2 роки тому

    Thanks a lot

  • @SCHEGS
    @SCHEGS 2 роки тому +3

    Thanks for this video, very well elaborated, but I also think that it's always good practice to share a link when referring to a previous video because a person must go to your channel and start looking for that specific video.

    • @AutomationCoreDev
      @AutomationCoreDev 2 роки тому +6

      Opening the playlist allows you to scroll through all videos in numbered order without having to navigate the channel. Also, allows you to see all videos related this playlist.
      Hope this helps.

  • @sandraosimen9630
    @sandraosimen9630 11 місяців тому

    Thank you so much !!!

  • @nikolavukovic5678
    @nikolavukovic5678 2 роки тому +1

    great content! thank you very much, god bless! radiyallhank!

  • @bsmangalarajapaksha7700
    @bsmangalarajapaksha7700 3 місяці тому

    Helpful. Thank you sir...

  • @LD-wf2yt
    @LD-wf2yt 2 місяці тому

    In order - not - to misunderstand and/or misapply the model, I suggest that the software industry professionals find a way to experience projects, systems, practices, flow etc in use in well-established companies in the construction industry i.e. the real thing. There is a lot of strong foundation built-in in preparation, plans, experience, clarity, transparency, risk management, housekeeping, quality etc going on in the real construction project than in the V-model of software development. An image of a strawberry is just that an image.

  • @TejaswiKon
    @TejaswiKon 2 роки тому +1

    You are explaining good.But voice is vry low.Try to overcome this in your coming videos.

  • @EndlesswarZ
    @EndlesswarZ 2 роки тому

    Hey sir, I think what pro parts you mentioned is W Model, which is an improvement based on V model.

    • @EndlesswarZ
      @EndlesswarZ 2 роки тому

      Actually V model (from what I learned ) is still follow phase by phase. The QA team will still waiting until coding part finish, then they will start unit test

    • @mahendrashewale900
      @mahendrashewale900 2 роки тому

      @@EndlesswarZ you are right but while doing verification we do validation parallelly. let take example while doing Information gathering at the same time we prepare UAT test plan and UAT test cases.

  • @ahmedtanvir9299
    @ahmedtanvir9299 Рік тому

    Give me a example of High level design and low level design.

  • @tinaye2573
    @tinaye2573 2 роки тому +1

    Thank you so much!