About Me

My photo
Jijitha Anand is an Software tester by Profession . She has 5+ years of testing experience.

Wednesday, October 30, 2019

Software Testing Life cycle

SOFTWARE TESTING LIFE CYCLE:-

Software Testing Life cycle is nothing but a sequence of activities done for testing software.
STLC is a series of activities carried out methodologically to help certify your software product. There are steps carried out to make the product bug free.



REQUIREMENT ANALYSIS
During this requirement analysis phase testers gather the requirement document. Tester goes through the document and discuss with the stakeholders if any question arises. In this phase what type of testing needs to be carried out is decided and Identifying test environment where testing is supposed to be carried out.
TESTPLAN
In this stage, effort and cost estimates for the project are to determine and would prepare and finalize the Test Plan. In this phase, Test Strategy is also determined. In his stage, the test plan/strategy document for various types of testing is prepared. Testing tools selection is done and effort for testing is estimated. The number of resources required and their roles and responsibilities is determined.
        TEST CASE DEVELOPMENT
In this phase test case is developed, test data is verified and rework on test case is done. Test data, is identified/created and is reviewed and then reworked as well in this phase.
This phase involves creating the test case and automation scripts. Reviewing the test case and scripts. Create test data which can be used for testing.

TEST ENVIRONMENT SETUP:-

Test environment decides the software and hardware conditions under which a work product is tested. Test environment set-up is one of the critical aspects of testing process and can be done in parallel with Test Case Development StageTest team may not be involved in this activity if the customer/development team provides the test environment in which case the test team is required to do a readiness check (smoke testing) of the given environment.

TEST EXECUTION:-

During this phase, the testers will carry out the testing based on the test plans and the test cases prepared. Bugs will be reported back to the development team for correction and retesting will be performed.

TEST CYCLE CLOUSER:-

Testing team will meet, discuss and analyze testing artifacts to identify strategies that have to be implemented in the future, taking lessons from the current test cycle. The idea is to remove the process bottlenecks for future test cycles and share best practices for any similar projects in the future.




Tuesday, October 29, 2019

Serverless Architecture


SERVERLESS ARCHITECTURE

Serverless architecture is also known as "serverless computing /function as a service (FaaS) " is a software design pattern where applications are hosted by a third-party service, eliminating the need for server software and hardware management by the developer. Applications are broken up into individual functions that can be invoked and scaled individually.

If a software application is hosted on the internet, it involves managing some kind of server infrastructure which means a virtual or physical server needs to be managed. Hence more resource and money is involved. But If we use a virtual server from a cloud provider we elimination physical hardware concerns, but still require managing OS and web server software processes. If we go for serverless architecture you focus purely on the individual functions in your application code.  It takes care of all the physical hardware, virtual machine operating systems, and web server software management. You only need to worry about your code.





Software Development Life cycle(SDLC)



SOFTWARE DEVELOPMENT LIFECYCLE (SDLC)


Software Development life cycle (SDLC) model is a conceptual framework describing all activities in a software development project from "planning to maintenance". This process is associated with several models, each including a variety of tasks and activities. SDLC is nothing but the life span of a software being built. 



Seven Phases of Software Development Life cycle:-

PLANNING:-
 In this phase team creates a well-detailed plan of action to be taken. In this phase Identification of the risks and technical feasibility study is done associated with the project. A various technical feasibility study is carried out so that the project is successfully implemented with minimum risks.
REQUIREMENT ANALYSIS:-
In this stage of the SDLC requirement of the client and the most effective solution to solve it is defined by the team. In this phase business representatives and IT, experts work hand in hand to understand client needs and understand each other's points of view. 
DESIGN:-
In this third phase role of software the architect comes into place and the role of a business representative reduces. Here IT experts together with software architect work together to create a layout of how the product should function and look. In the design phase team find the best solutions for the system they are going to create.
DEVELOPMENT:-
In this phase, the team starts creating the software. Knowledge gathered in previous stages is utilized here. The team tries to develop the products as per the client requirement. Once the product is crafted by the team BA's get involved to determine if the product meets the expectation or not.
TESTING:-
In this phase of SDLC, the team ensures the delivery of a product is of high quality. The product meets all the requirements and is bug-free. For a bug-free system, the team should check and kind of errors popping up, multiple tests should run to ensure that the system will work according to the design specification. 
DEPLOYMENT:-
In this phase, the software is released in the market. The deployment to the product even happens in stages. Before deploying in real-world software is made available for a few users for them to test i.e User Acceptance Testing(UAT). After UAT is done user feedback is taken into account and decided if the product is released or needs some enhancement. 
MAINTENANCE:-
When the product is realized it might encounter bugs and needs to be fixed, this is carried over in the maintenance phase. Sometimes the clients need some changes and improvement is carried out in the implementation phase.