Testing Methodologies & SDLC
Types of Testing
Dynamic testing-Testing in which we execute the product and find the defect
Static testing-Testing in which we don't execute the product but we can check whether all scenario is working fine based on design documents and code of the product
Smoke testing-Need to check basic and critical features are working perfectly, need to verify build verification testing, this testing is done by testing team
White-box testing-Its done by developer team, in this process evaluates the code and internal structure of the program
Black-box testing-Its done by testing team, in this process the external functional of the test object
Functional testing-Functional testing verifies that feature and system working as expected according to the requirements
Non-Functional testing-Non functional testing how well the system working based on (load and behavioral of the application, performance, stress and security )
Regression testing-Regression testing is the process of testing change to application to make sure that old and existing application still working with new changes
Sanity testing-testing is performed to check if there are no defect in the product before giving to the customer, this is also called deep level testing
STLC phases
Requirement Analysis-Requirement collections is done by product owner and product analysis
Testing Plan- All the future testing plan related to all activity (how many tester req, which test Engr is going to work with which module, how many days, which automation tools
Test Case developments-identify the possible scenario, write the test case , Need to review , Fixed review comments then approval
Test Environment setup-It is a combination of hardware and software environment on which the tests will be executed. It includes hardware configuration, operating system settings, software configuration, test terminals and other support to perform the test. It is the most crucial aspect of the testing process.
Test execution-will be having setup test case with you and will be having application by looking to the test case and marked the application passed or failed
Test Clouse -
Need for Test Closure
Stages of Test Closure
Test Closure activities
When are Test Closure Activities Performed
Test Closure Report
Benefits of Performing Test Closure Activities
Qualities that i possess:
Think for user: Product should be user friendly so i will pitch in my thoughts if i feel it will not be and provide alternate approaches to achieve what we want.
Reduce bugs: As i have vast knowledge about my modules that i work, i have mitigated product from bugs that might affect both the customer and the company.
Time management: i will start analyzing the requirement and write test cases when any enhancement is in design state so it will prevent from the defects