Task 1

·

6 min read

Q 1.

Software Testing -It is a process of evaluating a software application or system to ensure that it meets its specific requirements and functions correctly.

Mainly software testing is classified in to Manual Testing and Automation Testing.

Main Objectives of the software testing is to Identify and defects or bugs in the software before it is released to the end-users.

Different activities include like Planning, Preparation, Execution, Reporting of test results as it is performed to verify and validate the software against user business needs and industry standards.

We need to know why software testing is done;

# To ensure the specific requirements are met.

# To improve quality of the software.

#To reduce the risk of software failure.

#To ensure compliance with industry standards/guidelines.

#To increase customer satisfaction and confidence.

Different types of testing :

White box testing _It is mainly focuses on testing internal working of software. In this testing tester has access to the source code of the software, tests the software based on its internal structure, design and implementation.

Black box testing _It is used for validation mainly focuses on testing the software from the perspective of user without knowing the internal workings of the software. Tester only knows the inputs and outputs of the software based on the expected output.

Grey box testing _It is a method where you can use to debug software and evaluate vulnerabilities in this tester has limited knowledge of the workings of the component being tested.

  • ALPHA testing-Its is the beginning version of testing.

  • Beta testing - It is the stable version of testing.

  • Omega testing - It is the end version of testing.

    Basically Ten types of Testing listed below:

  • Unit Testing - It is the initial testing done, testing individual units or components of a software, typically done by developers to ensure working of the individual units we can say specific parts of the code is working fine is tested here.

  • Integration Testing - It is a testing how different units or components of a software application interact with each other.

  • Regression Testing - It is a method of testing is used to ensure that changes that changes made to the software do not get new defects or error in the existing functionality of the software Testing to verify that still works after the changes updated in the software.

  • Smoke Testing - It is a testing done to make sure that the software is working stable and ready for further testing.

  • Acceptance Testing - It is done by the customers to check the delivered products perform the desired tasks or not, as stated in the requirements.

  • System Testing - It examines every components of the application to make sure they work as complete it meets specified requirements.

  • Functional Testing - It is testing method that application feature works as per the requirements in software.

  • Security Testing - It is a testing method validate and verify the working effectiveness of application.

  • User Acceptance Testing - It is a method of final stage of testing before it is going for deployment as the product is bug free.

Q2.

  • STLC - Software Testing Life Cycle its a systematic approach is a systematic approach that it meets the requirements and its free of defects. To ensure that

    1. Requirement Analysis-It is the first step of a software testing life cycle. In this step QA team understands what are the requirements needed to be tested and all the clarity discussed with team and architect.

    2. Test Planning - In this step testing plans are discussed and clarity is given to the tester and plan of the requirement of cost and time effort required by team is confirmed. Regarding testcase and test data used also planned accordingly. Testing environment and resource required also planned.

    3. Test case Development-Once test plan is done development of test case starts, all the test cases are noted in detailed way and also reviewing of all the test case by the QA team is done.

    4. Environment setup-In this step it decides the conditions on which software tested this is set up by the developer or customer testing team is not involved.

    5. Test Execution-Once the test cases are ready and its all revised and looks good its executed in this step whether there any defects or issues. In test execution test results are documented and reported to the team.

    6. Test cycle closure- Its the last step in the STLC in this all the testing related activities are completed and documented. In this stage it makes sures its good for release and can move in to product region for release.

Q3.

As a manual tester i have worked in IT industry for two years, in these years i can proudly say that i have creative mind, strong analytical and problem solving skills helped me in finding bugs and in the right time error in the application found in the QA region and assigned back to the developer for rework he has to do in the code. Mainly communication skill i have helped me in communicating with the customer and the team for better output in project. Since have passion for Testing field i find m interesting. Reporting it as soon as there any error in the project immediately so that it takes no delay. Time management is the most important and efficient thing that i possess helped me in on time delivery with no delay. I'm a good team player so that collaborating skill i possess helped me in testing. Problem solving is the most important character in me helped in cracking all the scenarios in my testing.

Q4.

Waterfall methodology in SDLCAgile methodology in SDLC
1. Its also called as linear or sequential model. In this methodology things are done in top to bottom format.1. This methodology is a quick model we can say its the combination of incremental and iterative model-Agile paradigm.
2. Only once the previous phase has finished developing the next phase is starts, So changes can't be made after completion of a phase.2. In this product divided in to manageable pieces called as sprint. Changes can be made at any stage.
3. Client input is required only after completing each phase.3. Client input is required throughout the product development.
4. Team work is not needed as one team starts work after finish of another team.4. Team work is most important in this to complete the project on time.
5. It is mainly used for small project development.5. It is useful in complex and large projects.
6. It requires large team to complete.6. It requires small team to complete.
7. It is quite rigid.7. Its flexible in nature
8. The cost of development is high8. The cost of development is less.