EXplain TDLC

Hi All,

Can anyone tell me what is TDLC and how it is implemented?

cheers,
Sridevichitthu

Hi Deepa,

Thanks for the link

Its nice to see you progressing in number of post and queries especialy on QTP.

Cheers,
Sridevichitthu

hi friend..

Thanks i did nothing great ..I shared knowledge it may be useful to some one else, according to me knowledge develops by facing different real time scenario and bring out the solution for difficult scenario

Thanks
Deepasree

Hi how we answer a question - "explain your current project?"

hi friend..

just explain how you have designed and executed the test flow in your project

Thanks
Deepasree

Explain V-model of SDLC in detail?

hi friend

The V-model is a software development process which can be presumed to be the extension of the waterfall model. Instead of moving down in a linear way, the process steps are bent upwards after the coding phase, to form the typical V shape. The V-Model demonstrates the relationships between each phase of the development life cycle and its associated phase of testing.

Thanks
Deepasree

[QUOTE=deepasree;34416]hi friend

The V-model is a software development process which can be presumed to be the extension of the waterfall model. Instead of moving down in a linear way, the process steps are bent upwards after the coding phase, to form the typical V shape. The V-Model demonstrates the relationships between each phase of the development life cycle and its associated phase of testing.

Thanks
Deepasree[/QUOTE]
Totally agree with Deepasree, for more information you can check teh following site

[url=http://en.wikipedia.org/wiki/V-Model_(software_development]V-Model (software development - Wikipedia, the free encyclopedia[/url])

Hi Can any one give a brief explanation about FRAME WORK and its types?

[FONT=arial]a test automation framework is a set of assumptions, concepts, and practices that provide support for automated software testing<o>

</o>[/FONT] [B][U][FONT=arial]test script modularity frame work: <o></o>[/FONT][/U][/B] [FONT=arial]the test script modularity framework requires the creation of small, independent scripts that represent modules of the application-under-test. These small scripts are then used in a hierarchical fashion to construct larger tests, realizing a particular test case. <o>
</o>[/FONT] [B][U][FONT=arial]the test library architecture framework<o></o>[/FONT][/U][/B] [FONT=arial]the test library architecture framework is very similar to the test script modularity framework but it divides the application-under-test into procedures and functions instead of scripts. This framework requires the creation of library files that represent modules, sections, and functions of the application-under-test. These library files are then called directly from the test case script.<o>
</o>[/FONT] [B][U][FONT=arial]the keyword driven testing framework<o></o>[/FONT][/U][/B] [FONT=arial]keyword-driven testing framework requires the development of data tables and keywords, independent of the test automation tool used to execute them and the test script code that "drives" the application-under-test and the data. Keyword-driven tests look very similar to manual test cases. In a keyword-driven test, the functionality of the application-under-test is documented in a table as well as in step-by-step instructions for each test. It is an application independent automation framework.<o>
</o>[/FONT] [B][U][FONT=arial]the data driven testing framework<o></o>[/FONT][/U][/B] [FONT=arial]data-driven testing is a framework where test input and output values are read from data files (datapools, odbc sources, cvs files, excel files, dao objects, <st1:city w:st="on"><st1></st1></st1:city> objects, and such) are loaded into variables in captured or manually coded scripts. In this framework, variables are used for both input values and output verification values. Navigation through the program, reading of the data files, and logging of test status and information are all coded in the test script.<o></o>

[/FONT]regards,
bhaskar kumar
[FONT=arial][B]<o>
</o>[/B][/FONT]