#ScalaTest | Explore Tumblr posts and blogs

anantradingpvtltd · 2 years ago

Text

Price: [price_with_discount] (as of [price_update_date] - Details) [ad_1] "If I were to pick a language to use today other than Java, it would be Scala." —James Gosling Programming in Scala Fifth Edition is the definitive book on Scala, the popular language for the Java Platform that blends object-oriented and functional programming concepts into a unique and powerful tool for developers. Coauthored by the designer of the Scala language, this authoritative book will teach you, one step at a time, the Scala language and the ideas behind it. The book is carefully crafted to help you learn. The first few chapters will give you enough of the basics that you can already start using Scala for simple tasks. The entire book is organized so that each new concept builds on concepts that came before—a series of steps that promises to help you master the Scala language and the important ideas about programming that Scala embodies. A comprehensive tutorial and reference for Scala, this book will teach you the language and important libraries. If you read earlier editions, this fifth edition is a major rewrite of the book to cover Scala 3.0. Some chapters have been added and others removed. This edition describes Scala 3.0 in detail, including: · Enums and ADTs · Context parameters and givens · Extension methods · Quiet syntax and optional braces · Trait parameters · Union and intersection types · Export clauses · Top-level definitions Martin Odersky is the creator of the Scala language. He is a professor at EPFL in Lausanne, Switzerland, where since 2001 he has led the team that developed the Scala language, libraries, and compiler. He is a founder of Lightbend, Inc., and was a co- designer of Java generics and the author of the current javac reference compiler. Lex Spoon worked on Scala for two years at EPFL and is now a software engineer at Square, Inc. Bill Venners is president of Artima, Inc. He is a community representative on the Scala Center Advisory Board, and the designer of ScalaTest. Frank Sommers is president of Autospaces, Inc. Publisher ‏ : ‎ Goels Computer Hut/ Artima Inc; Fifth Edition (22 March 2022); Goels Computer Hut, 126, Budhwar Peth, Pune-411002 Language ‏ : ‎ English Paperback ‏ : ‎ 675 pages ISBN-10 ‏ : ‎ 8195098045 ISBN-13 ‏ : ‎ 978-8195098040 Item Weight ‏ : ‎ 850 g Dimensions ‏ : ‎ 10.5 x 8.5 x 2.5 cm Country of Origin ‏ : ‎ India Packer ‏ : ‎ Goels Computer Hut, 126, Budhwar Peth, Pune-411002 Generic Name ‏ : ‎ Inches [ad_2]

0 notes

0xfc963f18dc21 · 3 years ago

Text

thank you scalatest, very cool

there was definitely no other way I could have possibly gleaned what registerTest does /s

0 notes

bythebayio · 4 years ago

Text

Program Committee: Bill Venners.

youtube

Bill Venners is president of Artima, Inc., provider of Scala consulting, training, books, and tools. He leads the open-source projects for the ScalaTest testing library and the Scalactic library for functional, object-oriented programming. He is coauthor with Martin Odersky and Lex Spoon of the book, Programming in Scala. And he is a community representative on the Scala Center's Advisory Board.

How did you get into the software and what was your career arc like since then?

I was attracted to software because I felt it was a way to be creative that was also a realistic way to make a living. I started out as a programmer working in various cubicles, took a sabbatical to write a book about Java, and ended up doing software consulting, training, and book publishing.

What changed during the last year for you? How do you keep your enthusiasm for tech going?

I got a glimpse of a quieter life promised by retirement, and liked it. But I'm still quite enthusiastic about programming, so I want to keep working. I don't need to do anything to keep my enthusiasm alive. I find programming very interesting and want to keep doing more of it.

What tech is the most exciting for you? What projects have you found and liked so much that you shared them with friends?

Roller coasters are probably the most exciting tech for me. I recommend github to friends. I quite like using it and feel it does a great job at facilitating teams working on software.

Which people in tech are the most interesting to you? Who are some people you regularly keep in touch about tech?

I've spent a lot of time learning about type theory the past several years, so lately I've been reading a lot of papers and watching videos from people in that field. The tech people I keep in touch with are primarily people I've met through programming communities, mainly C++, Java, Python, and Scala.

How do you see conferences and meetups evolving after pandemic? Do you want to meet by the bay in person or stay online?

I want to meet in person again. Historically I often watched talks as videos later, spending most of my time at conferences talking to people in hallways. So I actually attended conferences both in person and online before the pandemic. I miss the in-person part.

We are happy to invite you to the 9th conference Scale By the Bay!

Format: Online Dates: 28th-29th of October 2021 Learn the schedule Register to attend Visit our website Join us on Twitter Watch the videos from the previous years for inspiration ;)

0 notes

snortingcode · 7 years ago

Text

SBT - Scala’s ((mistaken as) NOT SO) Simple Build Tool

The first thing that one notices when jumping into Scala development is its utterly complicated build tool. Complications arise due to several reasons (and reasons different for different people, I’m sure) but, a consistent gripe that people seems to have is the syntax used in the build definition file (typically build.sbt although, any *.sbt would work at the root of the project) for people not very familiar with some operators/constructors that the Scala community heavily relies on and, the monstrous amount of time it takes to get the first build started. The syntax seems strange at times even for Scala developers not familiar with sbt, that is because sbt is a DSL (Domain Specific Language). Let’s dive in to understand the essential basics!

[When I first ran “sbt run”, I wasn’t sure if things were even working at all, stared into the terminal for few 10s of minutes for several hours and nothing showed up. Google searches showed that it was a common problem! Although, in my case it was a conflict between the versions of Scala and sbt that were individually installed on my machine!]

With that welcoming note, let’s dive into the sbt world - it is bound to make your life easier if you know what you are doing. And it is an extremely powerful build tool.

I highly recommend that you read the sbt getting started guide completely before starting your project (this post is not a replacement as there are several details that are important and won’t be discussed here). I’m assuming that you’ve installed a recent version of sbt already. I’m writing this to provide a quick start (which might be a lot quicker than the “Quick Start Guide” that sbt documentation provides.)

Getting Started With “sbt new”

The recent versions of sbt (later than 0.13) provide a quick way to kick start your Scala projects -

$ sbt new sbt/scala-seed.g8

sbt uses g8 templates to create the basic structure of your project. There are tons of useful ones available and you can create your own as well. If you come from the Java world, think of these as Maven archetypes of sorts. The command above would ask you for some project details like the project name, my project’s name is: Whipp. (For reasons unknown to humanity!)

The previous command should set up a simple Scala project for you with a directory structure that resembles that used by Maven:

src/[main, test]/[scala, java, resources]

$ tree -L 2 . ├── build.sbt ├── project │ ├── Dependencies.scala │ ├── build.properties │ ├── plugins.sbt │ ├── project │ └── target ├── src │ ├── main │ └── test └── target ├── scala-2.12 └── streams9 directories, 4 files

The file that would the focus of our discussion in this post is the build.sbt file - the build definition.

(Don’t forget to add target/ to your .gitignore before you make your initial commit.)

Running the project:

Building and running the project is simple:

$ sbt #takes you to the sbt shell from where you can issue commands like run [info] sbt server started at 127.0.0.1:5522 sbt:Whipp> run #The task we wish to execute.

This would compile the project files and start the project. This could take a while if you are running your first project. Patience trumps hate!

Some cool things about the sbt shell are its tab-completion feature and history. It essentially behaves like your terminal’s shell. Pretty cool huh?

You could also provide tasks in a “batch mode” like this:

#takes sbt:Whipp> clean compile run

sbt provides a continuous build option. Append a task with ~ and sbt would watch for changes in your files, auto compile them and, execute the task - for instance, ~run would add efficiency to your development setup!

Here’s a list of all the commands available for you to use: https://www.scala-sbt.org/1.x/docs/Command-Line-Reference.html

The build definition - build.sbt

This is the most important and interesting section of this post so grab your coffee and read on! The key element in understanding the build.sbt file is that it is not just a properties file but, valid Scala code (well, valid sbt DSL code to be precise but, you get the drift!)

Read the generated *.sbt file with that perspective first and see what you can gather from it:

(Depending on which seed project you start with, this might look a little different. Hold on for a while and it would make a lot of sense to you!)

Let’s first look at what the below line is all about:

“lazy val root = (project in file(“.”))”

We are declaring a lazy value ‘root’ which happens to be everything followed by “lazy val root” in this case. Your build file is composed of several “val” and/or “lazy val”, these would typically fall under these 3 categories:

SettingKey[T]

TaskKey[T]

InputKey[T]

In fact, if you take a look at the config-classes under the target/ directory, you would find a cache file that has all the lazy val and val that you defined in your build.sbt file. You can also use the sbt shell to see what these keys are.

With that in mind, if you look at the build.sbt again, you’d see that we have a lazy val called root that contains the settings for each “project” in the current directory [project in file(“.”)]

Some of these are generic properties like the name of the project, organisation, etc. These are unlikely to change (it is a common practice to extract them out to a val and add it to the project.settings.)

In that sense, most of the build definition is just a bunch of key-value pairs => some help define things, some do interesting stuff. The value “name” is an example of a key that defines something.

A quick digression: If you try to assign a non-String value to “name”, you would get a typeMismatch error. The key “name” (which we did not define ourselves) comes along with the implied imports => sbt._, Keys._

Let’s try to add some interesting key that does something. Naturally, we would turn to a TaskKey[T]. Add these lines to your build definition:

lazy val doSomething = taskKey[Unit](“I do something cool!”)

Now, add this key to your settings. The updated build.sbt might look something like this:

import Dependencies._ lazy val root = (project in file(".")). settings( inThisBuild(List( organization := “com.snortingcode”, scalaVersion := "2.12.3", version := "0.1.0-SNAPSHOT" )), name := “Whipp”, libraryDependencies ++= Seq( scalaTest % Test), doSomething := {println(“Look what I did!”)} ) lazy val doSomething = taskKey[Unit](“I do something cool!”)

We defined a TaskKey[Unit] named doSomething using the method in the sbt DSL - taskKey[T]. Once you enter the sbt console (by restarting the sbt shell), you would notice that you can call this new task from the shell, simply by typing the task’s name - doSomething.

sbt:Whipp> doSomething Look what I did! [success] Total time: 1 s, completed 8 Feb, 2018 1:59:01 PM

You can thus, create a DAG (Directed Acyclic Graph) using these tasks and create a workflow for your project! Sweet!

A neat way to see what a task is doing is to “inspect” it:

sbt:Whipp>inspect compile [info] Task: xsbti.compile.CompileAnalysis [info] Description: [info] Compiles sources. [info] Provided by: [info] {file:/Users/prasoonjoshi/code/whipp/whipp/}root/compile:compile

(The actual output is rather long, so I’ve truncated it. Each [info] tells you important information about that task. (Try this out with the doSomething task you created just now and see if everything makes sense!)

We talked about the SettingKey[T] and TaskKey[T] a little bit, what is this InputKey[T] all about? Well, for now, you can just think of the InputKey as a method to take input from the user to create tasks on the fly (simple and powerful - we’ll talk about this in a future post soon!)

Let’s jump to the libraryDependencies

Yes, you know what they are! The essential information about this section of your build definition’s settings are:

+= is a method to append the provided dependency to the old libraryDependencies and return the new one!

libraryDependencies ++= Seq[<your list of dependencies>] is another way you’ll see the dependencies often defined in the build definition. (This is what our example build definition has.)

sbt uses Ivy for dependency resolution. The % that you see in the syntax below are sbt DSL’s methods that construct the Ivy module Id.

To define a new libraryDependency, you need to define the dependency first, then add it to the list of dependencies.

Here’s an example that adds mongo awesomeness to your project:

val mongo = "org.reactivemongo" %% "reactivemongo" % "0.12.6" libraryDependencies += mongo# # This line is part of my plugins.sbt file under the project directory. addSbtPlugin("com.typesafe.play" % "sbt-plugin" % "2.6.7") libraryDependencies += ws

Of course, you can add the val directly to the settings without declaring it first. See what works best for you!

I promised earlier that everything in your build definition is just a key (SettingKey, TaskKey, InputKey). See what the libraryDependencies key shows you on the sbt shell and see if that makes sense :)

A final note on the evaluation order in your build definition file: Since the build definition is just a DAG which is interspersed with “lazy val”, you should expect a sequential processing, with lazy val(s) evaluated only when they are required.

A point to keep in mind is that the SettingKeys are evaluated once, TaskKeys are evaluated each time the task is executed (these would usually have side-effects as you can see).

There are several beautiful aspects of sbt that we can’t explore here in this quick guide. I would encourage you to check out the documentation and Josh Suereth’s great talk on YouTube.

[Please do reach out to suggest improvements or corrections to this post :) ]

#sbt #Scala #functional programming #build tool

2 notes · View notes

dexfm · 8 years ago

Text

022: Functional Programming, ScalaMatsuri

引き続き@okapiesさんをゲストに迎えて、Functional Reactive Programming、関数型プログラミング、ScalaMatsuriなどについて話しました。

podcast feedを購読するか、DLしてお楽しみ下さい。

Show Notes:

「関数型プログラミングって何？」日本語訳 - Okapies' Archive

「なぜ関数プログラミングは重要か」を要約してみた（その１） - Okapies' Archive

Functional Reactive Animation

conal/talk-2015-essence-and-origins-of-frp: A keynote talk for LambdaJam 2015 (July 15--16)

Conal Elliott (@conal) | Twitter

ReactiveX - Intro

関数型プログラマのための Rx 入門（前編） - Okapies' Archive

モナド (プログラミング) - Wikipedia

世界で一番か二番くらいにやさしい「モナド入門」 - 檜山正幸のキマイラ飼育記

代数的データ型 - Wikipedia

null安全でない言語は、もはやレガシー言語だ - Qiita

Streams — Akka Documentation

オブジェクト指向とは何だったのか？ | ゆびてく

ScalaMatsuri 2017｜日本最大級の Scala のカンファレンス

Scala祭でscalatest作者とproperty based testingの話をした - scalaとか・・・

ScalaMatsuriの初社員採用プロジェクトこれまでの運営の失敗と成功の歴史 ~ScalaMatsuri 2017を振り返って~ - OE_uia Tech Blog

Contact:

@dexfmpodcast

@hydrakecat

@okapies

#dexfm

2 notes · View notes

grimrose7 · 6 years ago

Text

0 notes

bhanunune-blog · 6 years ago

Text

#2 Test Driven Development Using Scala

This post is continuation to series of posts on TDD using Scala. You can refer the previous post here.

In this post we would be dwelling into the details of available test frameworks in Scala.

Testing Framework

A testing framework is used for the automated testing of software. It is primarily a collection of postulations, perceptions and observations which support automated testing of application code. Its a misconception that testing frameworks are only intended for Unit testing but however they can be used for Integration, Smoke and Acceptance Testing.

Scala Test and Specs 2 are two main testing frameworks available and in the series of posts, we will be dwelling more into Scala Test Framework.

ScalaTest

Scala Test follows a JUnit style of test case writing which is not very verbose. It provides the flexibility of being able to write tests in various styles. This makes it a comprehensive framework for both BDD and TDD. It also integrates very well with various third party frameworks such as JUnit, TestNG, Ant, Maven and SBT.

Follow the Link if you are not sure on how to create a Scala project with maven dependency management.

Lets look at all scala styles briefly that ScalaTest supports.

FunSuite

It is good for the transition from xUnit with vivid test names.

import org.scalatest.FunSuite class AddSuite extends FunSuite { test("3 plus 3 is 6") { assert((3 + 3) == 6) } }

FlatSpec

structure of this style is flat - like xUnit, bu the test name can be written in specification style:

import org.scalatest.FlatSpec class AddSpec extends FlatSpec { "Addition of 3 and 3" should "have result 6" in { assert((3 + 3) == 0) } }

FunSpec

This is more analogous to Ruby's RSpec:

import org.scalatest.FunSpec class AddSpec extends FunSpec{ describe("Addition") { describe("of 3 and 3") { it("should have result 6") { assert((3 + 3) == 6) } } } }

WordSpec

This has similar structure to Specs2:

import org.scalatest.WordSpec class AddSpec extends WordSpec { "Addition" when { "of 3 and 3" should { "have result 6" in { assert((3 + 3) == 6) } } } }

FeatureSpec

It is primarily intended for writing BDD style acceptance tests. This allows for the use of ubiquitous language that can be understood by non-programmers.

import org.scalatest._ class Calculator { def add(a:Int, b:Int): Int = a + b } class CalcSpec extends FeatureSpec with GivenWhenThen { info("As a calculator owner") info("I want to be able add two numbers") info("so I can get a correct result") feature("Addition") { scenario("User adds two numbers") { Given("a calculator") val calc = new Calculator When("two numbers are added") var result = calc.add(3, 3) Then("we get correct result") assert(result == 6) } } }

Now that we know all available test frameworks in Scala, in the next post we will look at a problem statement and start writing the code using TDD Approach. Stay Tuned!!!

#scala #tdd

0 notes

hireindianpvtltd · 7 years ago

Text

Fwd: Urgent Requirements for below positions.

New Post has been published on https://www.hireindian.in/fwd-urgent-requirements-for-below-positions-3/

Fwd: Urgent Requirements for below positions.

We have an Urgent Requirements for below positions.

Please see the job details below and let me know if you would be interested in this role.

If interested, please send me a copy of your updated resume, your contact details, your availability and a good time to connect with you.

Security Consultant- ForgeRock SME——>Atlanta, GA

Technical Manager———>Pleasanton, CA

Java Full Stack Senior Developer——->Santa Barbara, CA

Quality Analyst———>Sunnyvale, CA

DevOps Engineers——–>Sunnyvale, CA

System Test Engineer——>Sunnyvale, CA

UI/Front-End Developer (Mobile Experience)—–>Frisco, TX

Lead Developer- Oracle Weblogic server——>Rosemont, Illinois

Job Title Location Job Description Security Consultant- ForgeRock SME Atlanta, GA

Duration: 1 year

Experience: 8 -14 years

Visa: USC/GC

Job Description:

The Senior ForgeRock Consultant will require a strong understanding of the ForgeRock suite of products. He or she will have good technical and soft skills. He would need to be a good starter particularly that of ForgeRock engagements and demonstrate good technical leadership in the implementation phase. The senior consultant will provide configuration and technical support for the in the design process to translate their unique requirements into technical designs for the system as also work through the implementation in a hands on fashion. He/she would also provide necessary thought leadership in the ForgeRock implementations.

Responsibilities

IAM planning and design aligned to client requirements.

Lead System development life cycle and environment management activities .

Design and develop provisioning and de-provisioning processes/workflows for accounts across various internal and external systems using the ForgeRock IAM stack.

Strong experience on Scripting tools like python, shell script.

Strong working knowledge on JAVA.

ForgeRock OpenAM and OpenIDM configuration & Customisations.

Experience of working on Cloud platform.

Work with the client business and application teams in integrating and on-boarding of applications in either of below.

OpenAM platform using policy agents, SAML(SaaS) or Webservices.

OpenIDM platform for provisioning/de-provisioning.

Technical Manager Pleasanton, CA

Duration: Long Term

Job Description:

Strong Python scripting developer with knowledge of infrastructure automation in Networking

5+ Years in IT Automation technologies

Good python scripting skills – 3+ years in Python development

Strong in Ansible (Mandatory)

Knowledge of TCP/IP and other networking protocols

Mandatory Skills: Python, Network Automation, Ansible, Network Protocols

Java Full Stack Senior Developer Santa Barbara, CA

Duration: Contract

Experience: 10 Years

Job Description:

Technology Stack: Extensive programming experiences in Java 8 (10 years minimum)

Proven experience in designing, developing and successful deployment of large scale Java/J2EE projects, utilizing best design patterns, tooling and coding practices.

Spring framework; Spring Boot; Spring web services – proficient, 7+ years

SOAP based web services – proficient, 7+ years;

· Familiar with Java messaging: AMQP (RabbitMQ), JMS – intermediate, 4+ year;

Frontend: Aurelia, HTML, JavaScript, CSS, Bootstrap, Template engines

Experience with Windows/Linux including Powershell, Python, or other scripting integration languages.

Must understand:

Object Oriented Programming (OOP)

SQL: MySQL, MS SQL Server;

Security: SSO, oAuth protocols; CORS, CSRF.

Expert knowledge of applications and programming functions with professional experiences in recent years.

In the areas of IAM space, broad/deep technology knowledge and the ability to develop a solution by mapping a customer's business problem to an end-to-end technology solution

10+ years' experience in integrating security and IAM products with common identity stores (LDAP, relational databases, application servers, virtual directory servers, and physical access management systems.)

Knowledge of AWS, ADFS, Azure AD and Cloud based authentication including MFA (Multi Factor Authentication) is a plus

Quality Analyst Sunnyvale, CA

Duration: Contract

Job Description:

QA in Hadoop HDFS, Kafka, ETL. Experience in QA of analytics on client side of data platform would be helpful

Key Qualifications

Familiarity with Hadoop, Cassandra, Kafka, Spark, Hive and other big data tools

Proven experience with Jenkins or similar CI systems

Experience in crafting and developing testing infrastructure for Distributed Systems, Big Data Platforms

Exceptional programming skills in Java, Scala, Python, or similar language

Strong software testing fundamentals and familiarity with Black Box, White Box and Performance testing

Exceptional analytical and problem solving skills

Experience using automated testing frameworks like Junit, TestNG, ScalaTest, Cucumber, JMeter, SoapUI, Gatling

Description

As part of this team, you will establish, implement and evolve the formal QA processes to ensure that the group is using industry accepted standard methodologies.

Design and develop the testing infrastructure i.e. testing tools, test frameworks, test reporting mechanisms to test the software, services, and Alternative data platforms of the team as well as the existing and new machine learning models build on the platform.

Integrate the testing infrastructure with the continuous integration and continuous deployment systems to ensure all of the tools, services developed are properly tested and meet the quality goals.

Write different types of tests i.e. Unit, Integration, and Acceptance for existing and new projects so as to ensure bug free software is delivered which is as per the requirements.

Stay knowledgeable of new testing tools and strategies and evaluate the technologies to incorporate into the projects.

DevOps Engineers Sunnyvale, CA

Duration: Contract

Job Description:

5+ years’ experience in DevOps with Ansible, Chef Puppet and build automation

System Test Engineer Sunnyvale, CA

Duration: Contract

Job Description:

5+ years’ experience in Linux/Unix- Shell scripting/Python/Perl/Ruby

A passion for diagnosing hardware, software, and process issues.

Demonstrated creative and critical independent-thinking capabilities and troubleshooting skills

Industry exposure to and knowledge of OS tools and UNIX internals. Know stuff like shell scripting, file system manipulation, process management, etc.

Experience with scripting languages such as Python, Perl, Ruby, shell scripts is required

Understanding of Object Oriented, Networking concepts is required

Experience working and debugging with Hardware is a plus

Ability to read and understand C or C++ code is a plus

We can get someone who has already done testing on Apple devices (including automation. Manual testing will not help) would be really helpful.

Additional details

Extensive programming using Objective C.

They should be aware of writing test cases using Objective C and very good idea of testing frameworks and device testing.

They should be aware of Object Oriented Programming Concepts using Object C or C++.

Design patterns are must if not worked with Object C.

Previous experience with device testing would be really helpful.

UI/Front-End Developer (Mobile Experience) Frisco, TX

Duration: 6 months

Job Description:

Deep experience in front-end technologies like HTML5, CSS3, Angular.ja, React.js

Ability to quickly turnaround prototypes for both web and mobile fron-end

Work closely with visual design teams to realize the clickable prototypes as required

Experimentation mindset and keen on learning new tools and technologies

Lead Developer- Oracle Weblogic server Rosemont, Illinois

Duration: 3-6 months

Job Description:

Application Server Oracle Weblogic server 11g,12c; Oracle Application server 10g; WebSphere, JBoss 4.1; WLS-JMS Server.

Web Server Apache Tomcat, MS IIS.

Database Oracle 10g/11i, MS Access, MS SQL Server. DB2 Blue Languages/Scripts Java 1.6, Java 1.8, J2EE, RESTful web services, Oracle Fusion Middleware Stack (ADF, ADF Mobile, Web center Suite,) JSP, JavaScript, CSS, HTML, JSON, AJAX, XML, XSLT, Jquery, Appache VM

Content Management Oracle UCM.

Change Management GITHub, SVN, VSS, Perforce

Tools/IDE

Middle ware

Frame Works IBM Data power XI50, Clover ETL 2.5.x, Putty, FTP (coreFTP and WINSCP), IBM LDAP, Caliber RM, Global scape, UC4 , Automic &UC4 , JIRA, ,Jenkins, (Splunk ,Puppet, Docker),Oracle Apex, Global scape, WSAD, Eclipse, Oracle JDeveloper studio 11 g. OTM,TOAD

IBM MQ 5.x, SFTP, IBM TDE 2.5

Oracle ADF, Enfinity Suite 6, Enfinity Suite 7, Struts 2.0

Operating Systems Microsoft Windows, UNIX, Linux

Thanks, Steve Hunt Talent Acquisition Team – North America Vinsys Information Technology Inc SBA 8(a) Certified, MBE/DBE/EDGE Certified Virginia Department of Minority Business Enterprise(SWAM) 703-594-5490 www.vinsysinfo.com

To unsubscribe from future emails or to update your email preferences click here .

0 notes

qoholiccom · 7 years ago

Text

Scala developer

Job Title: Scala Developer Location: Bentonville, AR Duration: Longterm Job Description: Excellent problem-solving, communication and analytical skills 5 + years of experience in Strong grasp of functional programming constructs and approaches, with a focus on Scala. 2+ years of Experience with Scala 2.10 or higher, SBT, ScalaTest, ScalaCheck The Light bend Stack: Akka, Play, Slick, Akka Streams Fluency with SQL and/or NoSQL databases: Postgres, Riak, Cassandra, HBase, MongoDB, etc. Reactive programming and principles Apache Spark, Hadoop, Steam Processing Kafka, RabbitMQ, Spring Integration/Batch, Camel Web Technologies: JavaScript, Angular, jQuery, React, HTML5, CSS3 Must have Micro-services Development experience Reference : Scala developer jobs source http://www.qoholic.com/index.php?page=item&id=2640

0 notes

jobsaggregationco · 7 years ago

Text

Scala developer

Job Title: Scala Developer / Platform Engineer Location: Bentonville, AR Duration: Longterm Job Description: Excellent problem-solving, communication and analytical skills 5 + years of experience in Strong grasp of functional programming constructs and approaches, with a focus on Scala. 2+ years of Experience with Scala 2.10 or higher, SBT, ScalaTest, ScalaCheck The Light bend Stack: Akka, Play, Slick, Akka Streams Fluency with SQL and/or NoSQL databases: Postgres, Riak, Cassandra, HBase, MongoDB, etc. Reactive programming and principles Apache Spark, Hadoop, Steam Processing Kafka, RabbitMQ, Spring Integration/Batch, Camel Web Technologies: JavaScript, Angular, jQuery, React, HTML5, CSS3 Must have Micro-services Development experience Reference : Scala developer jobs source http://jobsaggregation.com/jobs/technology/scala-developer_i2121

0 notes

jobrealtimeco · 7 years ago

Text

Scala developer

0 notes

mrzanko · 7 years ago

Text

Java Scala developer

Job Title: Java Scala Developer Location: Bentonville, AR Duration: Longterm Job Description: Excellent problem-solving, communication and analytical skills 5 + years of experience in Strong grasp of functional programming constructs and approaches, with a focus on Scala. 2+ years of Experience with Scala 2.10 or higher, SBT, ScalaTest, ScalaCheck The Light bend Stack: Akka, Play, Slick, Akka Streams Fluency with SQL and/or NoSQL databases: Postgres, Riak, Cassandra, HBase, MongoDB, etc. Reactive programming and principles Apache Spark, Hadoop, Steam Processing Kafka, RabbitMQ, Spring Integration/Batch, Camel Web Technologies: JavaScri...

Source: https://www.jobisite.com/sj/id/9037928-Java-Scala-developer

0 notes

jobisitejobsusa · 7 years ago

Text

Java Scala developer

0 notes

implicitly-notes · 7 years ago

Text

kiama 2.2.0

Kiama is a Scala library for language processing including attribute grammars, term rewriting, abstract state machines and pretty printing.

This is a maintenance release with only minor changes in functionality but splits the library into two pieces for publishing.

Potentially breaking changes

Kiama is now published as two separate libraries kiama and kiama-extras with the former containing just the core Kiama functionality and the latter containing extra support that is useful in many Kiama-based applications. At the moment, the kiama-extras library contains the Compiler, Config, Console and REPL components that are useful for building command-line configurable compilers and read-eval-print loops, plus the Kiama examples. In the new scheme clients can depend on one or both of these libraries, depending on their needs. Previously you got the extras (and their dependencies) whether you wanted them or not.

Output: To match standard code formatting styles, the seq pretty-printer now doesn't include a space after the prefix. E.g., what was previously printed as Seq (1, 2, 3) will now be printed as Seq(1, 2, 3). This change is also visible via the pretty-printers any and list which are defined in terms of seq.

Bug Fixes

Rewriting: The log and logfail strategies no longer have a default emitter argument since default arguments are not allowed on macro applications.

Util: The compiler, REPL and test drivers now give a sensible message when the command-line is illegal, rather than crashing with an exception.

Util: Separate Kiama suiteSourcePath setting from that used by clients of test code. The Kiama test suites now use the KiamaTests trait that sets suiteSourcePath appropriately for Kiama. The Tests suite now sets it to be suitable for clients who are using the default Scala project setup.

Other

Move to sbt 1.1.4, Scala 2.12.5, 2.11.12, 2.10.7

Update libraries to Guava 24.1, Scallop 3.1.2, JLine 2.14.6, ScalaCheck 3.0.5, ScalaTest 1.13.5, Scallop 3.1.2

Kiama is a Scala library for language processing including parsing, attribute grammars, term rewriting, abstract state machines and pretty printing.

#kiama

1 note · View note