Category: Published

Published content

Reduced Structural Complexity With Examples

berkkibarer

Code quality is -should be- one of the main concerns of a software developer. While designing the internal structure, it is important to avoid increasing the structural complexity -cyclomatic complexity, cognitive complexity, halstead volume, maintainability index and such…- which exposes to reliability, maintainability and testability problems. Factory pattern design seemed like a good place to start explaining how to work on complexity problems. The reason, Gürel and I picked factory pattern, is because its most common usage -no offense, this is just one way of doing it :)- simply turns…

UI TESTS FT. XPATH

berkkibarer

As seen on: TechQa.Com; Well, this post starts off with the basics first, but it will coincide with the title towards the end. I will try to convince you to switch your element locating practice from ids, class names, tag names … to XPath and will explain how this technique helps us test more efficiently. Common Usage The prevalence practice of UI testing is using “id”s when locating an element. If there is no id attribute for the element, new preference would probably be “classname”, “text” or so…And yet, at…

Load Test Correlation

berkkibarer

As seen on: Loadium.com;    In today’s world, we have to deal with various behaviors of systems while communicating with one another. In most cases, to carry on with test scenarios, we need to fetch the dynamic responses from preceding requests and pass it to the subsequent ones. By simply parsing and passing the needed data to the next caller provides a smooth transition during the test execution process (Load Test Correlation). Storyline: Since load/stress testing scenarios are based on mutual interactions between the client and remote, the need of…

Designing Test Plans with Controllers the Right Way

berkkibarer

As seen on: Loadium.com; JMeter Load & Stress testing might seem very straightforward with a little practice, but in big scale projects, things can get complicated. Test plans can be broken, it might be hard to keep the design clean, and it could become a burden for the team to maintain the flow in the long run. Like most things in life, the very same rule applies for JMeter: “Simple can be harder than complex” Steve Jobs. To create a well-organized and smoothly maintainable test in the long run, in this…