Hot answers tagged

2

Data driven tests work well when you have a lot of test cases that can be expressed as points in a parameter space. Some advantages of data-driven approach are: Test cases are easier to add or remove than when they are expressed as code You duplicate less test code and consequently are less susceptible to code/paste errors in your test code Someone other ...


2

There are many, many approaches, each having its pros and cons when it comes to simplicity of reading, easiness of modifying data, easiness of modifying data schema (refactoring), easiness of parsing data, type of data you want to model. If you were I would experiment. I would pickup the simplest approach (properties) to see if fits your problem. Here's the ...


2

First of all:There is no best approach. There are just several approaches and you have to decide which one is your favorite. What is the best approach to make test data configurable ? Through XML file or properties file or any other way. But must not be hard coded. I like it to put the test data in properties files, read the data and put them ...


2

In excel sheet always start with 0-column and 0-row and index 0 as well. Change data[i][0]=conf.getData(1, i, 0); data[i][1]=conf.getData(1, i, 1); data[i][2]=conf.getData(1, i, 2); to data[i][0]=conf.getData(0, i, 0); data[i][1]=conf.getData(0, i, 1); data[i][2]=conf.getData(0, i, 2);


1

For the time being Allure Framework is probably the most advanced reporting tool for testing. It has adaptors for many languages. It allows you to: Create steps and sub-steps in your tests. Sub-steps are good for detailed logging. Attach files like text files, JSON, XML, images, etc. You can view them right from the report in the steps. I think this is the ...


1

Software tools available for any task are very dependent on the language you use. You did not mentioned yours (my language of choice and reference is Python, one of the reasons is because it has such great tools and community). But most common languages do have most common tools, and all of the good ones are open-source and you can adapt/enhance them for ...


1

I do not claim to be expert, just try to do due diligence research before diving in, and use best practices, so... :-) IMHO start by trying to implement a pattern is wrong approach (trying to force pattern into solution). I start with "exploratory coding" and try to get the feeling what would be best approach (maybe after I have few years of experience with ...


1

I would tend to disagree with the comment of not designing and just coding. As with any testing you should aim to plan and find issues in requirements Before writing code. Its harder to change things later! I am quite a fan of Page Object Model (POM) as an approach http://seleniumeasy.com/selenium-tutorials/page-object-model-framework-introduction ...


1

Don't start with designing framework: YAGNI principle applies. Start coding. Implement tests, refactor common parts - and framework will emerge. Difference is, this framework will have only features you need. By definition, if you have to ask how to design a testing framework (don't already have skills to do it right), you should not try to foresee what you ...



Only top voted, non community-wiki answers of a minimum length are eligible