Ankit Gupta
Week-8
Software Testing Life Cycle

Contary to poular belief, software testing is not a just a single activity. it consists of series of activities carried out methodologically to help certify your software product. These activities constitute the software testing life cycle.
Requirent Analysis – during this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may interact with various stakeholders to understand the requirements in detail.
Activities- identify types of tests to be performed.
grater details about testing priorities and focus.
Test Planning- This phase is also called test strategy phase typically, in this stage, a senior QA manager will determine effort and cost estimates for the project and would prepare and finalize the test plan.
Test Case Development- this phase involves creation, verification and rework of test cases & test scripts. test data, is identified / created and is reviewed and then reworked as well.
Test Environment setup- Test environment decides the software and hardware conditions under which a work product is tested. test environment setup is one of the critical aspect of testing process and can be done in parallel with test case development stage test team may not be involved in this activity if the customer team provides the test environment in which case the test team is required to do a readliness check of the given environment.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit Gupta
Week-8
Software Testing Life Cycle

Contary to poular belief, software testing is not a just a single activity. it consists of series of activities carried out methodologically to help certify your software product. These activities constitute the software testing life cycle.
Requirent Analysis – during this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may interact with various stakeholders to understand the requirements in detail.
Activities- identify types of tests to be performed.
grater details about testing priorities and focus.
Test Planning- This phase is also called test strategy phase typically, in this stage, a senior QA manager will determine effort and cost estimates for the project and would prepare and finalize the test plan.
Test Case Development- this phase involves creation, verification and rework of test cases & test scripts. test data, is identified / created and is reviewed and then reworked as well.
Test Environment setup- Test environment decides the software and hardware conditions under which a work product is tested. test environment setup is one of the critical aspect of testing process and can be done in parallel with test case development stage test team may not be involved in this activity if the customer team provides the test environment in which case the test team is required to do a readliness check of the given environment.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit Gupta
Week-8
Software Testing Life Cycle

Contary to poular belief, software testing is not a just a single activity. it consists of series of activities carried out methodologically to help certify your software product. These activities constitute the software testing life cycle.
Requirent Analysis – during this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may interact with various stakeholders to understand the requirements in detail.
Activities- identify types of tests to be performed.
grater details about testing priorities and focus.
Test Planning- This phase is also called test strategy phase typically, in this stage, a senior QA manager will determine effort and cost estimates for the project and would prepare and finalize the test plan.
Test Case Development- this phase involves creation, verification and rework of test cases & test scripts. test data, is identified / created and is reviewed and then reworked as well.
Test Environment setup- Test environment decides the software and hardware conditions under which a work product is tested. test environment setup is one of the critical aspect of testing process and can be done in parallel with test case development stage test team may not be involved in this activity if the customer team provides the test environment in which case the test team is required to do a readliness check of the given environment.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit Gupta
Week-8
Software Testing Life Cycle

Contary to poular belief, software testing is not a just a single activity. it consists of series of activities carried out methodologically to help certify your software product. These activities constitute the software testing life cycle.
Requirent Analysis – during this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may interact with various stakeholders to understand the requirements in detail.
Activities- identify types of tests to be performed.
grater details about testing priorities and focus.
Test Planning- This phase is also called test strategy phase typically, in this stage, a senior QA manager will determine effort and cost estimates for the project and would prepare and finalize the test plan.
Test Case Development- this phase involves creation, verification and rework of test cases & test scripts. test data, is identified / created and is reviewed and then reworked as well.
Test Environment setup- Test environment decides the software and hardware conditions under which a work product is tested. test environment setup is one of the critical aspect of testing process and can be done in parallel with test case development stage test team may not be involved in this activity if the customer team provides the test environment in which case the test team is required to do a readliness check of the given environment.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit
Week-7

Test Automation Language

Community management filed all the notifications for all the tester for the quater.lately is  seems whenever you turn on the radio, tv or looked at the newspaper flyer, you can’t avoid the back to school sals. I notice you explicitly sidestep this question in your article, but generally, the compiled languages have much more powerful capabilities that the scripted languages do not exception handling, multithreading, synchronization, namespaces to manage complexity, XML support. I struggled with Ruby on a legacy project for months. No, Ruby doesn’t even come close to doing what I needed it to do, but more on that below.
From extensive technical discussions on what is possible with Python, I think it’s close, but not quite there, and it’s definitely a poor choice for a large, complex project.
Generally, scripting languages are widely used for “test automation” but their limited capabilities restrict them to an outmoded understanding of what that automation is all about and where it brings business value – really, the answer to the question “Why are we doing this?”
C or C++ can probably do it, but it’s been a while since I’ve used those languages. Java can do it, too, if you don’t need realtime, but my preference is C# which is more modern, better-designed, much better libraries, and more OO than Java.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit
Week-7

Test Automation Language

Community management filed all the notifications for all the tester for the quater.lately is  seems whenever you turn on the radio, tv or looked at the newspaper flyer, you can’t avoid the back to school sals. I notice you explicitly sidestep this question in your article, but generally, the compiled languages have much more powerful capabilities that the scripted languages do not exception handling, multithreading, synchronization, namespaces to manage complexity, XML support. I struggled with Ruby on a legacy project for months. No, Ruby doesn’t even come close to doing what I needed it to do, but more on that below.
From extensive technical discussions on what is possible with Python, I think it’s close, but not quite there, and it’s definitely a poor choice for a large, complex project.
Generally, scripting languages are widely used for “test automation” but their limited capabilities restrict them to an outmoded understanding of what that automation is all about and where it brings business value – really, the answer to the question “Why are we doing this?”
C or C++ can probably do it, but it’s been a while since I’ve used those languages. Java can do it, too, if you don’t need realtime, but my preference is C# which is more modern, better-designed, much better libraries, and more OO than Java.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit
Week-7

Test Automation Language

Community management filed all the notifications for all the tester for the quater.lately is  seems whenever you turn on the radio, tv or looked at the newspaper flyer, you can’t avoid the back to school sals. I notice you explicitly sidestep this question in your article, but generally, the compiled languages have much more powerful capabilities that the scripted languages do not exception handling, multithreading, synchronization, namespaces to manage complexity, XML support. I struggled with Ruby on a legacy project for months. No, Ruby doesn’t even come close to doing what I needed it to do, but more on that below.
From extensive technical discussions on what is possible with Python, I think it’s close, but not quite there, and it’s definitely a poor choice for a large, complex project.
Generally, scripting languages are widely used for “test automation” but their limited capabilities restrict them to an outmoded understanding of what that automation is all about and where it brings business value – really, the answer to the question “Why are we doing this?”
C or C++ can probably do it, but it’s been a while since I’ve used those languages. Java can do it, too, if you don’t need realtime, but my preference is C# which is more modern, better-designed, much better libraries, and more OO than Java.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit
Week-7

Test Automation Language

Community management filed all the notifications for all the tester for the quater.lately is  seems whenever you turn on the radio, tv or looked at the newspaper flyer, you can’t avoid the back to school sals. I notice you explicitly sidestep this question in your article, but generally, the compiled languages have much more powerful capabilities that the scripted languages do not exception handling, multithreading, synchronization, namespaces to manage complexity, XML support. I struggled with Ruby on a legacy project for months. No, Ruby doesn’t even come close to doing what I needed it to do, but more on that below.
From extensive technical discussions on what is possible with Python, I think it’s close, but not quite there, and it’s definitely a poor choice for a large, complex project.
Generally, scripting languages are widely used for “test automation” but their limited capabilities restrict them to an outmoded understanding of what that automation is all about and where it brings business value – really, the answer to the question “Why are we doing this?”
C or C++ can probably do it, but it’s been a while since I’ve used those languages. Java can do it, too, if you don’t need realtime, but my preference is C# which is more modern, better-designed, much better libraries, and more OO than Java.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit
Week-7

Test Automation Language

Community management filed all the notifications for all the tester for the quater.lately is  seems whenever you turn on the radio, tv or looked at the newspaper flyer, you can’t avoid the back to school sals. I notice you explicitly sidestep this question in your article, but generally, the compiled languages have much more powerful capabilities that the scripted languages do not exception handling, multithreading, synchronization, namespaces to manage complexity, XML support. I struggled with Ruby on a legacy project for months. No, Ruby doesn’t even come close to doing what I needed it to do, but more on that below.
From extensive technical discussions on what is possible with Python, I think it’s close, but not quite there, and it’s definitely a poor choice for a large, complex project.
Generally, scripting languages are widely used for “test automation” but their limited capabilities restrict them to an outmoded understanding of what that automation is all about and where it brings business value – really, the answer to the question “Why are we doing this?”
C or C++ can probably do it, but it’s been a while since I’ve used those languages. Java can do it, too, if you don’t need realtime, but my preference is C# which is more modern, better-designed, much better libraries, and more OO than Java.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ankit
Week-7

Test Automation Language

Community management filed all the notifications for all the tester for the quater.lately is  seems whenever you turn on the radio, tv or looked at the newspaper flyer, you can’t avoid the back to school sals. I notice you explicitly sidestep this question in your article, but generally, the compiled languages have much more powerful capabilities that the scripted languages do not exception handling, multithreading, synchronization, namespaces to manage complexity, XML support. I struggled with Ruby on a legacy project for months. No, Ruby doesn’t even come close to doing what I needed it to do, but more on that below.
From extensive technical discussions on what is possible with Python, I think it’s close, but not quite there, and it’s definitely a poor choice for a large, complex project.
Generally, scripting languages are widely used for “test automation” but their limited capabilities restrict them to an outmoded understanding of what that automation is all about and where it brings business value – really, the answer to the question “Why are we doing this?”
C or C++ can probably do it, but it’s been a while since I’ve used those languages. Java can do it, too, if you don’t need realtime, but my preference is C# which is more modern, better-designed, much better libraries, and more OO than Java.

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.