People who code: we want your input. Take the Survey
13

In addition to reading Working Effectively with Legacy Code, I have a few recommendations from experience: Since there is little to no documentation, tour the software. Go through the software using it as if you were a user, noting what it does and what you can find about why it works the way it does. Talk to long-time users. Since this is internal software,...


4

Reference material- Working Effectively with Legacy Code by Michael Feathers The books discusses working with legacy systems, not just testing them. Some of the suggestions are using a module's Logical complexity, Dependency level and Priority to decide on what to test. It then suggests two approaches as to what to start with- easy first or hard first, both ...


4

Although I don't have a complete answer this question is special, the difference from the common "how do I test" questions is the high frequency of changes. Testing everything thoroughly is one approach, but as @vicky99 explained it's not worth investment for a very short lived feature. There two approaches to go as I see it. One approach that ...


1

You can use the Heuristic Test Strategy Model as a starting point to design your approach for testing (a mindmap version can be found here). By laying out the Project Environment, you will realize the boundaries and limitations of the project. Product Elements will help you to understand the components of the product, which you can then do risk analysis and ...


1

I would recommend using Allure report with Detox. - see this link for more details. It gives good insights into the test execution metrics with readily available and configurable metrics With VS Code, Live server extension, you can launch an allure report every time you run with one click - which is super easy Also You can visualise historical trends of ...


1

It depends If you're testing Tableau and you're after a commercial solution, have a look at Kinesis CI. I haven't personally used the tool but I've seen teams in my organisation use it for their reports (though they eventually moved on from it to building their own Selenium framework). If you're testing Power BI, you don't have a lot of options that I'm ...


1

It is difficult to fixate on common automation strategy for these kind of features from an automation testing services perspective. A better approach would be take them on case by case terms. For example, it will be better to automate a feature that will stay for 4 weeks than the ones that are expected to be discontinued after 1 week. Another factor to be ...


1

It looks like a question between the tradeoff between the cost/effort/speed of manual testing and automating the feature. I assume that you have nice commit-stage verification tests. It means that the part of your feature definition of done is covering the feature with unit and integration tests, regardless of whether it would stay in your app, or would be ...


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