Important Question

Requrement Traceability Matrix:
                                                       It is indicate the matrix set a table the table is shows as many to many relation requirements and test cases.there is multiple requirements and multiple test cases.

         "Requirement Traceability Matrix or RTM captures all requirements proposed by the client or development team and their traceability in a single document delivered at the conclusion of the life-cycle".
Type of RTM 


Forward Traceability:
                                      This matrix is used to check whether the project progresses in the desired direction and for the right product. It makes sure that each requirement is applied to the product and that each requirement is tested thoroughly. It maps requirements to test cases.
    1)Business requrement
Backword Traceability:
                                      It is used to ensure whether the current product remains on the right track. The purpose behind this type of traceability is to verify that we are not expanding the scope of the project by adding code, design elements, test or other work that is not specified in the requirements. It maps test cases to requirements.

Forward and Backword Traceability:
             It is used to ensure whether the current product remains on the right track. The purpose behind this type of traceability is to verify that we are not expanding the scope of the project by adding code, design elements, test or other work that is not specified in the requirements. It maps test cases to requirements.

Methodologies:                    

                     There are lots of methodologies and models that are used for software development and testing. As an experienced and modern-thinking software testing company, TestFort implements the most efficient and future-proof testing methodologies to allow our clients to choose the most suitable one for their testing needs.

Agile Methodology:

A software testing practice that follows the principles of agile software development is called Agile Testing. Agile is an iterative development methodology, where requirements evolve through collaboration between the customer and self-organizing teams and agile aligns development with customer needs.
Scrum is an iterative and incremental agile software development framework for managing product development.

Advantages of Agile Testing

• 1)Agile Testing Saves Time and Money
  2)Less Documentation
  3)Regular feedback from the end user
  4)Daily meetings can help to determine the issues well in advance.

   "Agile testing is used whenever customer requirement are changing dynamically. 

                          If you have no SRS, BRS but we have test cases does you execute the case blindly or do what follow other process"


SDLC:SDLC is Software Development LifeCycle, it is a systematic approach to develop a software.
STLC: The process of testing a software in a well planned and systematic way is known as software testing life cycle(STLC).
1)Requirements gathering:Requirements Analysis is done is this phase, software requirements are reviewed by test team.
2)Design:Test Planning, Test analysis and Test design is done in this phase. Test team reviews design documents and prepares the test plan.
3)Coding or development:Test construction and verification is done in this phase, testers write test cases and finalizes test plan.
5)Testing:Test Execution and bug reporting, manual testing, automation testing is done, defects found are reported. Re-testing and regression testing is also done in this phase.
6)Deployment:Final testing and implementation is done is this phase andfinal test report is prepared.
7)Maintenance:Maintenance testing is done in this phase.

Waterfall model:

    Waterfall model consists of the following phases:

       1)Requirements analysis:

       2)Design

       3)Implementation

       4)Verification

       5)Maintenance

Iterative model:    

Waterfall model consists of the following phases:

     1)Requirement

     2) Design& Development

     3)Testing

     4)Implementation

 

Bug Life cycle: 

          Bug life cycle is the different stages through which a bug passage during its life cycle the different stage are-

           a)New

           b)Open/Assigned/Delvivered/Fixed

           c) Return/Rejected

           d)Cancel

           e)Retest

           f)Retest Passed

           g)Return Failed

           h)Duplicate

           i)Reopened