Agile Scaling and its Challenges

[suchona.kani.z]

Finally, companies working toward agile scaling need to address their technology stack. Scaling agile across the enterprise requires transparency, visibility, and information flow, and drives those things simultaneously. For most companies, that means evaluating and potentially extending or replacing technology solutions.

You can find out more about agile scaling in the insurance industry on our website .

You can find more exciting topics from the adesso world in our previously published blog posts .

Markus Felkel works at adesso as a Scrum Product Owner. In this role, he is responsible for requirements management in agile projects. As a pragmatic product owner, he uses his empathetic stakeholder management to capture the customer's actual wishes and conveys feasible solution ideas.

Jenny Gursch works at adesso as an Agile Coach. In this role, she namibia consumer email list coaches our customers on questions about the agile mindset, methodology and practices and builds software development teams with agile best practices and frameworks. Her expertise lies in the establishment and development of agile teams using SCRUM and KANBAN, coaching the surrounding management and generally promoting the agile mindset in the corporate environment.The problem is familiar to almost every front-end developer: a simple unit test becomes incredibly complex due to the implementation details. This brings with it some disadvantages, which is why Angular has provided Component Harness since version 9.

What problem does Component Harness address?
As mentioned above, tests can quickly become confusing due to implementation details. This can lead to the basic idea that a test should represent the desired behavior being lost or the effort to understand the use case being increased.

An example: We want to implement a component that renders a datepicker and displays the selected date in appropriate formatting. The use case sounds trivial and we would expect the test to consist of a few lines of code, right? The button for opening the datepicker can be given an ID and is therefore easy to select in the DOM. However, the complexity increases enormously when the datepicker is displayed in an overlay, as Angular Material does, for example. At this point, the test must be based on the implementation of the component.