Learning to code is hard. Learning to code with tests is harder. Let's practice this art together.
Writing automated tests for your code is a development technique, which should be done by the people writing the SUT. Sort of like building a car with the dashboard sensors built in rather than somehow trying to put them into a car after you already manufactured it.
Getting into "testing" as far as being a professional exploratory tester/test lead (which what I do), you could get into it like I did (by having a degree in something unrelated and talking your way into the job) or you could do the BBST course(s) which would probably help a lot (I didn't do that)
Cool defining it. What I meant by testing is just the way devs hear "testing"
Do they write automated checks?
It probably differs from workplace to workplace. My company has been around since the 80s and when they hear "testing" they think of handing it to the QA department so that people can find bugs and hand it back.
but a lot of newer web companies are talking about writing unit/integration/UI tests.
Natalie J. Bennett
@reywinters03 Are you having a hard time convincing devs you work with to look into testing? What's your goal here?
@njbennett no I'm not trying to convince the people I work with. I'm trying to help the general public ... There are many devs out there that likes testing but don't know where to start. Or have their own ideas of what testing is. Or managers that want testing but don't know how to get his/her team to start. Or even ones who have been writing tests to help refine the skill ....
I want a hybrid place where it doesn't matter what your title is. If you're writing software to test other software this place should be able to help refine, educate and/or kickstart the process
Hey, guys. I have some questions :) we are using Testrail (for checklists) - Screenshot1. When I was writing specs in Gherkin for mobile app i used signs to mark from TestRail like ‘C165’ for future tracking - Screenshot2. For navigation specs (to check all ‘back/forth’ buttons) i was thinking to write separate test-scripts. And i developed transitional diagram - Screenshot4. How to correctly divide/include all functionalities on test scripts (negative/positive) correctly - for easily maintaining in future, not for redoing that. I understand that's pretty vague question, maybe you could give me some clues. Do you know is it possible to connect BDD scripts to Jira, so it can automatically upload the bug and make a screenshot. All screens: https://www.dropbox.com/home/Screens I would appreciate any help
That link doesn't have anything user specific in it so it definitely does not link to your screenshots.
But - with apologies - I don't know anything about JIRA and any APIs it has for creating new bugs with screenshots but based on other experiences I believe that it does have one.
It would be a matter of calling that API with whatever Gherkin-parsing scripting tool you're using.
UNRELATED: do people unit test their UI and integration tests?
@rutr1ka I don't see any screenshots so I'm going to try to answer as best I can ... Using the page object pattern will help with your scalability. As for jira you might be able to write
@vsComputer_twitter I haven't heard of anyone unit testing their ui and integration tests but that's interesting ... Testing your tests ...
Anyone have a good way to lint commits?
Yep ... eslint? And git hooks?
Natalie J. Bennett
We had some test-like code around some really complex test setup in a Rails project I worked on, but in general we try to keep test code as simple as possible.
Pivotal projects actually don't even go in for
Page objects that much
At least on the Cloud Foundry side. Though we don't have as much experience with front end projects. I'll ask some Labs pivots.
@reywinters03 yep, was going to suggest just that thing
sigh appium ...
this is not fun stuff
Hey Guys :) do you have an idea how to reify that http://www.quri.com is rendering header text correctly.
make assertion for the title of the main header?
@aabdullin What is considered correct for header text? If you just want to assert the text is there. expect(document.querySelector('.selector-for-header').textContent).to.equal('foo'). What tech stack are you confined to?