QATestingJourney

 Difference between regression, sanity and smoke tests Regression test: It is a type of application testing that is used to verify any modification or update in an application without affecting the overall working functionality of the said application. It is usually done at the last stage of UAT.  Sanity test:   It is a subset of regression testing. After receiving the software build, sanity is to ensure the code changes introduced are working as expected.  Smoke test: It is a quick test to run through the application to ensure each function is working according to the business requirements. Normally, it takes 10-15 minutes to run through the application. 

 What is non-functional tests? It is to verified how well an application perform.  Non-functional test include the following: Source from:  Non-Functional Testing: Types,Process,Requirements,Differences |Professionalqa.com

Testing types Software Testing Hierarchy 1. End to end testing:  is to test the functionality and performance of an application under product-like circumstances and data to replicate live settings. The goal is to simulate what a real user scenario looks like from start to finish.  It is a crucial step for an application. 2. Acceptance testing: Also known as User Acceptance Testing. It is conducted by users where they provide the requirements, prepare test cases, execute test cases and ensure all the defects are being closed before signing off the UAT.  They need work closely with the business analyst, project managers or other key stakeholders.   System testing: System testing examines every component of an application to ensure they work as a complete and fully integrated. This is to verify if the system works as expected or not. Usually QA team conducts system testing after it checks individual modules with functional or user story testing and then each component...

 What is defect management? How do you log a bug? It is to manage the defect of the application and to resolve the bugs on a timely basis. The following information needs to be included.  We must give meaningful information and make necessary assessment on each defeat.  Defect ID Defect summary Defect description - simulate the defect steps to reproduce the same error. Log down all the expected and actual results plus all the other relevant information. The information here is critical as it allows developer to know the issue before fixing the bug(s). Severity - product manager/owner or user needs to access/risks and what level of impacts to the business. Priority - impact analysis must be carried out  Environment - testing or production environment? Assigned to Status Images - Error message  Popular defect management tools  Excel file  SpriaTeam,  Jira Azure AWS How to prioritize a bug? It is very much depend on the severity of the bug....

What is STLC? STLC stands for software testing life cycle. It is a process used by the project teams to ensure the quality of the applications are being met.  As we can see in the software testing life cycle, there are various stages within the cycle.  Stakeholders or product owners provide the business requirements. QA manager carries out the test planning including the resources, budget, goals etc. Testing team has to ensure the application meets the quality of the applications. There are different types of testing methodologies could be used but best fit model(s) must be selected. In this way, it helps the business to save time and cost.  List of test suits, scenarios test cases must be defined before executing the test. Once the test cases are passed, we can close the the testing and move to production. In fact, in reality, due to time constraint, we must priority the test cases so that it will not affect the production.  

 What is SDLC? SDLC stands for software development life cycle.  It consists of different stages from planning to production. Business follows this cycle to develop their applications. Previously, when I was working in banking industry, we used waterfall methodology to carry out the projects. If our customer added a new feature to the product, it would go through different stages as seen in the diagram.   The stakeholders came together to define the scopes and requirements. For example, the customer requested to add the stock margin feature in the existing system.  Project managers or stakeholder would have a resource plan to estimate the budget as well as accessing the product risks. It needed approval from sponsors. For large corporate companies, they would select user representatives  to define the user requirements. They then design the test scenarios, test cases, test suits, and conduct the user acceptance testing. The IT manager would write the t...