18

A good starting point is to define what quality means in your context. And then find out ways how to measure it. It seems you want to measure something without saying what that something is. Having said that, we can hardly tell you that here, but perhaps we can give you some starting points that you might use in discussions with your teams and other people ...


14

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,...


9

I recommend One set of tests You've clearly defined a common problem that many of us face. I have tried all of the solutions you outlined but they all seem to run into the issue of a lot of maintenance and knowledge and updating code based on environment. My recommendation is one set of tests. If there are dependencies, e.g. database you create a connection ...


6

What would you do? I'd most likely hand in my notice working in such an environment. Is there any reason why this has to be overengineered? Not in my opinion. I'd simply create one test case and trust my coworkers. They should be able to communicate when it's needed. Of course getting access to all three systems is a priority (it is really necessary in fact)...


6

For me it is about measurable faster delivery of valuable features, while reducing downtime of functionality. I think good products and teams go faster and faster overtime. This might be different than most people have experienced, typically software projects go slower and slower overtime. Which I would say is due to "bad quality" in Functional, ...


6

In situations like described I like to test for business goals instead of strict requirements. Your application has a certain function and implementation can either support it in achieving that function or hinder it. Any hindrance would be treated as a defect (to be filtered through the product owner since some implementations that to not directly support ...


4

Communicate. Early and often For this release Be open. Assess the situation as best you can but be sure to pull in the rest of the team and get their input, advice and opinions. Err on the side of over-communicating and most of all don't let fear stop you from being honest. Using a good communication form - slack, teams, etc. may be better than long ...


4

What about the three of you sit down and... work together? You can simply plug one computer in a screen and you all test it together. (No sarcasm, seriously) Two of the tags you posted are "HP-ALM" and "Jira". It can be a guess, but I feel that you may be limiting you way of working because of how these tools are setup. From the Agile ...


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

There could be hundreds of examples, to name just a few: automated releases to test and other environments test data generation performance tests (hardly possible without tools that automate some load) text parsing, e.g. I need to create a JSON out of XML, so I use tools for that, I need to change a newline character from CRLF to LF, so I use some tools for ...


3

Since you have Session-Based Test Management, you can use your test sessions data to show your team's testing capacity. For example: You can plot the number of sessions your team did throughout time. Downtrends may intigate your team is having problems to keep a steady pace or that your testability has improved, demanding less test sessions for the same ...


3

These are the metrics our company uses in priority order: Number of support cases per number of active users Number of errors generated and logged by our application This covers a number of underlying aspects of software development: How user friendly is the product? If it's not then you get more support requests and or less users. The more errors logged, ...


3

The test strategy describes how - the overall test process, the techniques and practices used, design of test cases, selection of cases for retesting or regression, management and maintenance of the test environment, and the tools to support all of these. In some cases, the test strategy may also describe who - the structure of the test organization, who is ...


3

for your information, the functionality of drag and drop is back, in the new interfaces the action is different between the tabs "Define" and "Execute", you need to be on "Define" tab to use drag and drop.


3

Requirements are rarely complete, not necessarily because people are sloppy but because we figure things out as we create them. So good Testers should always read requirements with a critical eye and employ other test strategies as well. Having said that, it's important to create an environment where people actually work together and Testers have access to ...


2

I test a web-based product and am good at exploratory testing, scenario testing, do proper analysis, know database SQL queries and try my best to find critical problems in functionality, but don't use programming or tools. I wonder how you access a database without tools... I think you already use a lot of tools, bez perhaps you are not aware of that. Do I ...


2

Testers in the Agile world are not the only ones doing the actual testing. They should be looked at as testing coaches for the whole team, improving testing in various ways, like proposing good testing practices, making acceptance criteria more testable, etc. Since it is difficult for you to be an effective tester because of the "this software works&...


2

I don't think anything exists out of the box. You will probably need to write some steps that use a RabbitMQ client (amqp-client) to check if there are events on the queue etc...


2

The screenshot you provided is not a Testcase but a bug report. You cannot consider a personal blog as final point of truth , it can be the authors mistake or a unnoticed mistake while uploading file to that web page. Now coming to your actual question, there is no much difference between writing testcase in a Test Case management Tool and a Excel file. ...


2

The Defintion of Ready and Done is very context, risks and team depended. Depending on the quality needs of the product you might need more or less in these definitions. There is not a one size fits all. That is why I would suggest you sit down with your team and write down what information you need to start on work (ready) and what DoneDone means for your ...


2

There's no one answer to this. It's highly dependent on the context in which you are working. For example, I've worked in fields with varying degrees of regulation, where traceability from requirement and change through test case execution is vital. In these cases, having a test case documented in a test case management tool and selecting appropriate test ...


2

In testign everything is context depended . Its hard to suggest merits and demerits unless you states the following things like : What methodology you work in (Agile or waterfall ?) What is your sprint length How much time you gets for testing What is your responsibility ( Is it only manual , is it automation or is it both) What is the Team size What is the ...


2

I work in an environment where we have many environments but they're all part of a single release pipeline, i.e., features are first deployed to dev and they progress through all environments until they reach production. I can imagine some organisations might have different environments that are connected to different downstream systems, which possibly ...


2

Your question is very general and the answer depends on many factors such as organization rules, AUT's (Application Under Test) business, Test methodologies, type of tests you want to automate and ... But there is one key concept in test automation named Test Pyramid introduced by Mike Cohn. You should climb up the triangle as necessary as you want and for ...


2

You are looking for a dynamic, runtime, solution because like you wrote a static analyzer can only go so far. A good solution, but not 100% accurate (*), could be mutation testing combined with a dynamic code coverage tool. Descartes: A Mutation Engine for PIT is such a solution but it is Java only and might not work well in high performance systems. (*) ...


2

Lets answer from a experienced QA perspective. Testing is not an after thought , it is a process that needs to be integrated to all stages of SDLC. We have moved a long way from waterfall model where we waits for information or final product implementation to start testing. We also have moved away from agile where we used to split the entire project ...


2

This will likely change according to a context. You might find it unnecessary to even have such a document, because your organisation perhaps works in Agile where we generally prefer working software over comprehensive documents. Also the teams in an Agile environment tend to be small (seven plus minus two is a number that's usually mentioned as ideal), ...


2

How did you guys set up your vulnerability regression testing? I have used static analysis tools like HCL AppScan and SonarQube. These run against your source code and can be set up as "checks" in GitHub, Azure DevOps, etc. When and how do you deploy the regression tests? You can use a dynamic scanning tool like SortSite or ZAP. How did you use ...


2

Implement 3 amigos sessions I would implement precisely 3 amigos sessions in this situation to develop an shared understanding as team for below: Business- What problems are we trying to solve? Development- How might we build a solution to solve this problem? Testing - How could we possibly test this solution effectively? What could possibly go wrong which ...


1

If you want to setup your own cross-browser testing environment you could look at using Selenium Grid, have look here: https://www.lambdatest.com/blog/selenium-grid-4-tutorial-for-distributed-testing/ In the grid you install nodes (machines) that contain a fixed version of a browser, where you install a fixed version of the driver. Maintaining your own grid ...


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