Author Topic: Can You all please guide me with the Practical Steps of STLC followed by company  (Read 1035 times)

Offline tanushri_mukherjee70

  • Jr. Member
  • **
  • Posts: 1
  • Karma: +0/-0
    • View Profile
I am not aware with the practical software testing steps followed in a company. Can you please guide me with the same. :)

Offline Anitha Kaasam

  • Full Member
  • ***
  • Posts: 19
  • Karma: +0/-0
    • View Profile
In small companies
Their is no proper cycle
But Requirements sent to the tester and And tester analyze requirements
Start testing the application and Mention the bug in the document
And send those to the Developers again
This is continue until the client satisfies

advertisement

Offline vimalbabu

  • Full Member
  • ***
  • Posts: 15
  • Karma: +0/-0
    • View Profile
Hi,


Most of the small companies are following Iteration and Prototype models based on customers requirment.

Some big companies are following Spiral model.

Some companies are following the new technology. that is "Agile".

In all the models the process sequence is Requirement -> Design -> Coding -> Testing -> Maintenance. This is a cyclic process till the customer satisfaction

Offline Hare_Krsna16

  • Jr. Member
  • **
  • Posts: 5
  • Karma: +0/-0
  • Jai Sri Krishna :)
    • View Profile
yes sure why not but be patient kkk

Offline dheerajs

  • Full Member
  • ***
  • Posts: 33
  • Karma: +1/-0
    • View Profile
Different organization uses different STLC. But now a days water fall model is not used as this has many drawbacks.
V- Model is used in many organization where testing and development is done simultaneously.
Some company are also using Agile model in present.

In general
SOFTWARE TESTING LIFE CYCLE - PHASES
Requirements study
Test Case Design and Development
Test Execution
Test Closure
Test Process Analysis

Offline abhinav_u

  • Jr. Member
  • **
  • Posts: 5
  • Karma: +0/-0
    • View Profile
The universal steps for testing are-
1. Get the requirements
2. Analysis over them
3. Create test cases
4. Execute test cases
5. If test case is pass than close it or if it is fail than make a defect log and forward to developers to fix it.
6. After fixing that defect perform retesting and than regression testing.
7. Now if it is pass than close otherwise again forward to developers this cycle will repeat until test case is not pass.