Views: Create tests for organization_feed.dart

[palisadoes]

• Please coordinate issue assignment and PR reviews with the contributors listed in this issue Student Internship Programs #359

The Talawa code base needs to be 100% reliable. This means we need to have 100% test code coverage.

Tests need to be written for file lib/views/after_auth_screens/feed/organization_feed.dart

• When complete, all methods, classes and/or functions in the file will need to be tested.
• These tests must be placed in a single file with the name test/views/after_auth_screens/feed/organization_feed_test.dart. You may need to create the appropriate directory structure to do this.

IMPORTANT:

Please refer to the parent issue on how to implement these tests correctly:

• Complete Code Coverage for Views #1217

PR Acceptance Criteria

• When complete this file must show 100% coverage when merged into the code base. This will be clearly visible when you submit your PR.
• The current code coverage for the file can be found here. If the file isn't found in this directory, or there is a 404 error, then tests have not been created.
• The PR will show a report for the code coverage for the file you have added. You can use that as a guide.
• You can verify your own code coverage by creating an account at Codecov.io
• No functionality must be removed to achieve this goal

[harshitraisahab]

i wolud like to solve this issue please assign to me

[noman2002]

Unassigned due to inactivity.

[Ayush0Chaudhary]

@noman2002 @palisadoes @TheHazeEffect please assign this issue to me!

[Ayush0Chaudhary]

I am facing a issue solving this issue.

talawa/lib/view_model/after_auth_view_models/feed_view_models/organization_feed_view_model.dart

Lines 51 to 67 in 311b205

	void initialise() {
	// For caching/initalizing the current organization after the stream subsciption has canceled and the stream is updated
	_currentOrgName = _userConfig.currentOrg.name!;
	// ------
	// Attaching the stream subscription to rebuild the widgets automatically
	_currentOrganizationStreamSubscription =
	_userConfig.currentOrgInfoStream.listen(
	(updatedOrganization) =>
	setCurrentOrganizationName(updatedOrganization.name!),
	);
	_postsSubscription =
	_postService.postStream.listen((newPosts) => buildNewPosts(newPosts));
	_updatePostSubscription =
	_postService.updatedPostStream.listen((post) => updatedPost(post));
	}

the above code uses a stream and set value of _post variable

But all the test written return null, I was not able to find a test where actual post list was returned

@noman2002 @palisadoes can you help me with this

I have achieved 90% coverage but small part require the actual post to test

talawa/lib/views/after_auth_screens/feed/organization_feed.dart

Lines 60 to 64 in 311b205

	model.posts.isNotEmpty
	? PostListWidget(
	key: homeModel?.keySHPost,
	posts: model.posts,
	function: model.navigateToIndividualPage,

[Ayush0Chaudhary]

talawa/test/widget_tests/after_auth_screens/events/explore_events_test.dart

Lines 158 to 178 in 311b205

	testWidgets("Testing if tapping on calendar works", (tester) async {
	await mockNetworkImages(() async {
	locator.unregister<EventService>();
	final StreamController<Event> _streamController = StreamController();
	final Stream<Event> _stream =
	_streamController.stream.asBroadcastStream();
	final service = MockEventService();
	when(service.eventStream).thenAnswer((invocation) => _stream);
	locator.registerSingleton<EventService>(service);
	final homeModel = locator<MainScreenViewModel>();
	await tester.pumpWidget(createExploreEventsScreen(homeModel));
	await tester.pumpAndSettle();
	expect(
	find.text("Looks like there aren't any events."), findsOneWidget);
	});
	});

one posiible solution is this but it return a null value

[palisadoes]

@noman2002 @TheHazeEffect Do you have any thoughts on how to resolve this?

[Ayush0Chaudhary]

@palisadoes @noman2002 @TheHazeEffect I implemented this and 11 is getting printed but same thing is not happening in its viewmodel
Their is a problem with the scope of Mock
Can you help me with this??

[Ayush0Chaudhary]

@literalEval can you suggest something??

[literalEval]

@Ayush0Chaudhary I believe your reference of the view model is different then the one that the widget is using, I mean both are different instances.

I was having the same issue while writing tests for a widget and I worked it around by referencing the view model used by the widget directly.
Something like

late VM _vm;
....
....
BaseView<VM> (
  onModelReady: (model) {
    _vm = model;
  }
)

This way you can be sure that you are referencing the exact same view model.

[Ayush0Chaudhary]

@literalEval You can try on this issue.

[literalEval]

Sure. I will take this issue once I am done with the issues I am already assigned with.

[Cioppolo14]

This is reopened because test coverage for this file is not acceptable.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[Cyclotron17]

Can you please assign this issue to me.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[Cioppolo14]

Unassigning due to inactivity.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[github-actions]

This issue did not get any activity in the past 180 days and thus has been closed. Please check if the newest release or develop branch has it fixed. Please, create a new issue if the issue is not fixed.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.