I work with a manager who does not conduct any devops, no source control, no system diagrams, no code reviews, no scrum, no unit testing framework, no architectural plan, this is my first job out of college, something does not feel right. How would I tell manager, maybe we need these things above? Thinking it may make him angry. Company has around 2000 employees, I work at a software data warehouse department.
I am already using Terraform to provision and deploy the resources (infra +Serverless).I am thinking to split Serverless from the infra provision. And Serverless could be deployed along with TESTING via AwS codepipeline or other similar tool.
What is your feedback to use AWS SAM or Serverless framework with CI/CD ? Which is better and easily configurable.
Does SAM has good edge being aws native services ? I can see benefits of SAM for publishing serverless application in repository which can be reused and deployed (but that can be done via CI/CD) so not sure about the benefits.
Hello everyone! I wanted to let everyone know that the Unit Testing Framework I made for GMS2 now officially supports 2.3.0! It also now has a marketplace asset, so if you're not interested in downloading it from the github page, you can do so there.
Github: https://github.com/pmarincak/gms2-test
Marketplace: https://marketplace.yoyogames.com/assets/9280/gms2-test
I hope this is useful to you all! And let me know if you have any questions or comments!
I've always kind of hacked my code together and had the attitude like testing was for chumps. Lately I've had a change of heart and a realization that unit testing is pretty important. I see Mocha and Should in a lot of places but it's always nice not to have unnecessary deps for my package. Why not just stick with the assert lib that ships with node? What make these other frameworks so popular?
I've used cmock before. Are there any frameworks out there that people are using instead? Particularly, what's your opinion on having to have separate implementation files for each function so you can mock dependencies?
Anyone have a favorite? Trying to decide between a few different ones right now. Junit is winning but I wonder if folks have other thoughts.
Also, on Junit- which version is standard? 4 or 5?
I released version 1.0 of doctest 4 months ago.
Today I'm happy to announce version 1.1 - which comes mainly with bugfixes and compile time improvements!
check out the /r/cpp thread for the discussion
Mention others in comments.
Announcing a new version of GUT. GUT is a Unit Testing framework for the Godot Game Engine available via GitHub and the Godot Asset Library. Version 6.8.3
- Added filenames to "got" and "expected" values. For example you'll see
[Node:1234](my_script.gd)now instead of just[Node:1234] - Text is now wrapped in the display. If you hate it let me know and I'll add a flag.
- Various bug fixes
Links
- https://github.com/bitwes/Gut/releases/tag/v6.8.3
- https://godotengine.org/asset-library/asset/54
- https://github.com/bitwes/Gut/wiki
- https://github.com/bitwes/Gut
Tutorials:
- https://github.com/bitwes/Gut/wiki/Tutorials
Coming from a puppet and powershell background, in developing modules in either I used rspec or pester to do test-driven development. The configuration tests for expected configuration were written before the actual code to perform changes, and then bundled with the module for future development. Does anyone know of exemplars of test-driven development of ansible playbooks and roles?
Writing test cases, and then confirming that the code actually set things as expected has been a huge help in development. It also has been really valuable for cases when things are done manually (outside of automation for whatever reason) to provide a standalone 'configuration checker'.
What is the ansible equivalent? I have seen a tests directory inside of some roles, but they seem generally more like smoke tests (syntax test \ run without an error) vs. being able to create test cases, apply the configuration, and finally validate the actual configuration matches the expected.
I'm trying to figure the best way to unit test GetHumanPlayerShot and CreateComputerShot private methods in the code sample below. They don't need to be public, so making them so would break open / closed principle in SOLID.
Whats the best way to unit test private methods? is there a way to check they are called with a unit test and check the result? I can mock out RandomLocationGenerator.Generate(0,10) as that implements an interface.
For brevity, ive omitted some code / classes in my example code
The only public method that needs to be exposed is RunGame as it returns the gameState.
Should i make methods public to make them testable or is there a better way?
public interface IBattleShipGameStateMachine
{
GameState RunGame();
}
public class BattleShipGameStateMachine : IBattleShipGameStateMachine
{
public BattleShipGameStateMachine(IGame game, IConsole consoleWrapper, IRandomNumberGenerator randomLocationGenerator)
{
this.ConsoleWrapper = consoleWrapper;
this.Game = game;
this.RandomLocationGenerator = randomLocationGenerator;
this.ValidShotTester = new Regex(@"\d+,\d+", RegexOptions.Compiled);
this.gameState = GameState.NotStarted;
}
private GameState gameState { get; set; }
public GameState RunGame()
{
this.gameState = GameState.GameRunning;
IPlayer playerOne = this.Game.Players.First(p => p.PlayerNumber == 1);
IPlayer playerTwo = this.Game.Players.First(p => p.PlayerNumber == 2);
while (!this.gameState.Equals(GameState.PlayerOneWon) && !this.gameState.Equals(GameState.PlayerTwoWon))
{
// human and computer take turns shooting
Location shot = this.GetHumanPlayerShot();
if (this.gameState.Equals(GameState.PlayerExit))
{
break;
}
// logic omitted here to check if ships hit / all ships sunk etc
Location shot = CreateComputerShot();
}
return this.gameState;
}
// creates a location x,y. need to unit test this to ensure its a valid location
private Location CreateComputerShot()
{
int x = this.RandomLocationGenerator.Generate(0, 10);
int y = this.RandomLocationGenerator.Generate(0, 10);
Location shot = new Location(x, y);
TL;DR Looking for examples of unit-testing in whatever programming language you're familiar with.
I'm reading through How to Design Programs and came across this line:
> One day you will switch to another programming language; one of the first tasks will be to figure out its unit-testing framework.
The text gives a clear example of how to set up unit tests using Racket, noting that the check-expect statements can be above or below your function definitions. But when glancing at other frameworks like Python's unittest and doctest, the examples are less clear. Can anyone provide some unit-testing examples in languages other than Racket?
Bonus: how much attention do people place on their unit testing?
