In this episode, Agata and Karolina, QA at Scalac are going to tell you:   

- an analytical strategy based on the model  

- methodological strategies  

- reactive strategy (based on errors found in the application - the strategy should be updated as the project progresses)  

- consultative strategies (in cooperation with the client)    

- regressive strategies (reducing the risk of regression, writing automation tests for regression is also an approach)    

The #testingstrategy is for a tester is the first step to create a test plan, to the overall outline of how we will test, what testing approach we will choose for the project. A strategy does not have to be a document, it can be an approach.   

What is the difference between a test strategy and test plan?  

 TESTING STRATEGY is an outline that applies the testing methods of the software development cycle.  It is created to inform project managers, testers, and programmers about various issues related to the testing process. 

This includes  

- the goal of the research 

- methods of testing new functions  

- total time and resources available to implement the project, as well as the test environment  

TEST PLAN - #testplan is a document describing the scope, approach, resources, and schedule of intended test activities. 

It identifies amongst others 

 - test items,  

- the features to be tested,  

- the testing tasks,  

- who will do each task,  

- degree of tester independence,  

- the test environment,  

- the test design techniques,  

- entry and exit criteria to be used, and the rationale for their choice, and any risks requiring contingency planning.   

Main aspects included in the testing strategy:  

- product risks  

- the testing model which will be a tool to mitigate these risks  

- goals 

- responsibilities  

- main tasks  

- test case design techniques  

- input and output criteria 

 - approach to automation for each level of testing  

- standards that must be fulfilled  

- the level of test independence  

- test environment  

- approach to regression testing

https://scalac.io/rest-assured-api-testing-tutorial-java-scala/ 

https://scalac.io/manual-testing-590-timezones-2-days/ 

https://scalac.io/performance-testing/ 

https://scalac.io/testing-for-mobile-apps/

Why you should choose ZIO in your next project. Benefits of functional programming in ZIO In this episode, you will find out why the principles of Scala should be applied everywhere.    Mat Gren, Head of Business at Scalac, and Zuka Kakabadze, CTO at Fugo, talk about the business benefits of using functional programming and, most importantly, ZIO - Type-safe, composable asynchronous and concurrent programming for Scala.    Fugo is a #startup that chose functional programming and ZIO to scale its #MVP. See what the business reasons behind this decision were. Also, find out why it's a great approach to think longterm. To think about Scalability from day one and build your scalable MVP in Scala.

Here's a quick preview of the topics we'll cover in the episode:

In this video, you're going to learn precisely how working from home in an IT company looks like.    

In our opinion, the ability to effectively work from home is THE most important skill you can have now in coronavirus outbreak. Lukasz Kuczera, AKA HANS, CEO of Scalac, and Senior Scala Developer Michal Szulczewski share their best tips on how to work remotely, representing two sides of the fence.

Employer

- lower costs - have more autonomous employees

- make better use of technology

- #IncreaseProductivity

- access to a wider pool of applicants

- improve employee retention

Employee

- having a flexible schedule

- create a custom environment that suits your needs

- avoid office distractions - save time on commuting

- make calls without searching for a free conference room

Specifically, in this video, you'll learn from our CEO and our Developer:

How to set up hardware, tools, boundaries, your work environment to get the best results.

Then, we'll show you how employees and employers can work together on the "Is he really working?" issue. And give you some tips and tricks on time management working from home.

When it's all said and done, you'll have a specific knowledge of working from home showed from both the CEO and Developer side.

Want to know more about working from home?  Download our ebook on How to Manage Remote Employees for FREE!  https://bit.ly/2Ua4HdQ

In this episode of our podcast, you'll see 5 of our Scala Developer - Daniele Torelli -  best tips on working remotely.   

So if you want to get comfortable working remotely, you'll love the actionable techniques in this video.  

In short, you'll get access to a bunch of Working From Home tips that you can (literally) implement today.

Functional Programming is consistently gaining market share, and its popularity is growing.

Why is that?

Answer for CEO: Because Functional Programming goes exceptionally with business and scalability. In functional programming, there's less code, and there are fewer dependencies, so it enables you to develop different parts of your system/business independently. Especially in complex systems, it's the only reasonable way to scale.

Answer for CTO: Functional programming means: Less code, fewer bugs, code open for parallel computation, and concurrent programming.

But what you'll learn in this episode of our podcast is that it's not about throwing away your object-oriented program to enter functional programming.

We're going to help you find your approach, whether you're a beginner or more experience in functional programming concepts.

Here's some of the stuff we're going to cover in today's episode.

How #FunctionalProgramming is helping the #business

Strongly typed and statically typed Functional Languages

Differences between strictly typed and dynamically typed languages

Benefits of Functional Programming:

Object-oriented vs. functional programming - why some companies still choose object-oriented languages?

Ways teams can start building projects in a more functional approach

Scala evangelist that creates a team from scratch

The whole company decides to shift to Functional Programming

Simple steps you can take to be more functional - changing the way the team thinks about the code

#DomainDrivenDesign, #EventSourcing, #CQRS (Command Query Responsibility Segregation) functional nature

Advice for more experienced teams

How to switch to functional programming on JVM - from JVM to Scala

Why are people still not choosing functional programming as their first choice?

Changes in functional programming communities - FP gaining popularity.

ZIO library by John De Goes - a simple solution to get functional programming benefits without the hassle

Conclusions about Functional Programming future - is it going to become mainstream?

How to build a fully remote company? Is it easy to work with a #remotecompany on a project?

We decided to find out. And the results will probably surprise you.

First, a little bit of background. Scalac is a remote company (with most of our 122 employees working remotely). CloudAdmin has been Scalac's client for almost three years. Also, Paweł Gieniec, CEO of CloudAdmin, build his company based on remote culture.

We decided to ask Paweł how building a remote company looked for him. We talked about #cloudsystems and #datacenters, in general, but also considering the #COVID19 situation. Then Paweł talked thoroughly about building his company and working from home. Also, we tackled the trust in working with remote agencies; thus, it's very often a concern of people who never worked with such a company before. Finally, we talked about building culture in a remote team and the influence of the external organization that joins your company. Does it affect culture? Which scenario is better - when the number of employees is growing inside or outside your startup?

Find out!

In this episode, we're going to talk about Keycloak authorization.