LaxmiAcademy

https://www.youtube.com/watch?v=2yPpaez1MPk Manual Testing  is a process carried by testing team to find the defects  and to confirm that application works as per the requirements. Testers manually execute test cases without using any automation tools. Tester plays an important role as end user and verify all features of the application work as per requirements. Identify any unexpected behavior or bug Manual testing is necessary find feasibility of automation. 100% automation is difficult task for any software. In Manual testing the designed test cases or test scenarios will be executed and any differences between actual and expected results are reported as defects. Once the reported defects are fixed, the testers will retest the defect to make sure that the defects are fixed It is preferable to execute User Interface test cases using manual testing. Manual testing is slower than automation. Running tests manually can be very time consuming. What is Automated Testi...

https://www.youtube.com/watch?v=3EWghmo9Mfg   1. What is SDLC? Answer: SDLC, Software Development Life Cycle is a process used by software industry to design, develop and test high quality software that meets or exceeds customer expectations. 2. What are The different models of SDLC? Waterfall Model Agile Model Prototyping Model Iterative Model Spiral Model V-Model Incremental Model 3. What are the different types  of software requirements? Business Requirements (BR): High level Market Requirements (MR ): high level drilling down into BR Functional Requirements (FR) – Functionality of the product Non-Functional Requirements (NFR)- Reliability, Scalability, Security, Integration, etc. UI Requirements (UIR ): Market Requirements (MR) and  UI Requirements (UIR) are not included in traditional software requirements.   4. Why do software have bugs? SDLC involves humans at all levels which make software prone to human errors and also technical error...

https://www.youtube.com/watch?v=9isF5oZP_hA Desktop application runs on personal computers and work stations, so when you test the desktop application you are focusing on a specific known environment. Since the environment is known compatibility testing for desktop application is fairly easier. In client server application, application is loaded on server machine while the application executes on every client machine. Compatibility testing becomes little bit complex since it needs to be tested at 2 levels. Web application is loaded on the server but location and environment of users is unknown. Since users environment is unknown multiple conditions need to be considered while testing web application which makes it complex. Compatibility is a non- functional testing and goal is  to determine whether your software application or product is efficiently working and stable to run in different browsers ,hardware, screen size, resolution, operating system, mobile devices, users and networks. ...

https://www.youtube.com/watch?v=9isF5oZP_hA From the software testers point of view it is very important to verify that the software performs its basic functions as per the requirements, but it is equally important to verify that the software is able to gracefully handle any abnormal situations or invalid data input which helps to determine stability of the software. Negative Testing is performed to find the situation where there is possibility of software to crash. Last thing you want to see is software crashing at end user hand. so Negative testing plays an important role in testing software.  It is a negative approach, where testers try to design test cases to find the negative aspects of the application and validating against invalid input. Example: Phone number: User can enter alpha numeric characters in phone number field. so system should display error message like " Phone number should be numeric" Another example can be : Age: User can enter negative numbers or alphan...

https://www.youtube.com/watch?v=Jd8c6zlbwEQ Functionality Testing Usability testing Interface testing Compatibility testing Performance Testing      Load testing      Stress testing      Soak testing      Spike testing Security Testing Web Applications are open to the world with potentially multiple users accessing the application simultaneously at various times, so load testing and stress testing are important. Web applications are also vulnerable to all forms of attacks, so security testing is also very important to consider when testing web application.

https://www.youtube.com/watch?v=FeihVtO8GBM Manual Testing  is a process carried by testing team to find the defects  and to confirm that application works as per the requirements. Testers manually execute test cases without using any automation tools. Tester plays an important role as end user and verify all features of the application work as per requirements. Identify any unexpected behavior or bug 100% automation is impossible In Manual testing the designed test cases or test scenarios will be executed and any differences between actual and expected results are reported as defects. Once the reported defects are fixed, the testers will retest the defect to make sure that the defects are fixed It is preferable to execute User Interface test cases using manual testing. Manual testing is slower than automation. Running tests manually can be very time consuming.

https://www.youtube.com/watch?v=v548wJC62jE The process of validating and verifying that a software program or application or product work as expected. Software meet the business and technical requirement The only objective of software testing is not to find software bug that exists, but to identify situations that could negatively impact the customer, usability of software.

https://www.youtube.com/watch?v=h9RvPN3kiHk&feature=youtu.be   Testing of individual software components or units or modules. Typically unit testing is done by the programmer and not by testers. Unit is smallest and complete set of code which accepts input, processes and gives output The primary goal of unit testing is to take the smallest piece of testable software in the application, isolate it from the remainder of the code, and determine whether it behaves exactly as you expect.